View Full Version : dualboot windows F12
lemtree
17th December 2009, 09:26 AM
I have installed F12 on the remaining space on my disk and now Windows does not boot anymore.
I get to Grub and choose windows and then just get black screen with flashing cursor.
Am I or have I done something wrong?:confused:
glennzo
17th December 2009, 09:31 AM
The boot loader is probably trying to boot Windows off of the wrong partition. Can you post the output of
su
/sbin/fdisk -l
cat /boot/grub/menu.lst
lemtree
17th December 2009, 09:53 AM
[root@server1 ~]# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x7a3f085b
Device Boot Start End Blocks Id System
/dev/sda1 1 9728 78140128+ 83 Linux
Disk /dev/sdb: 82.0 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x69205244
Device Boot Start End Blocks Id System
/dev/sdb1 1 3547 28491246 7 HPFS/NTFS
/dev/sdb2 * 3548 3573 204800 83 Linux
/dev/sdb3 3573 9964 51339752+ 8e Linux LVM
Disk /dev/dm-0: 50.6 GB, 50591694848 bytes
255 heads, 63 sectors/track, 6150 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 1979 MB, 1979711488 bytes
255 heads, 63 sectors/track, 240 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
[root@server1 ~]# cat /boot/grub menu.lst
cat: /boot/grub: Is a directory
cat: menu.lst: No such file or directory
[root@server1 ~]# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x7a3f085b
Device Boot Start End Blocks Id System
/dev/sda1 1 9728 78140128+ 83 Linux
Disk /dev/sdb: 82.0 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x69205244
Device Boot Start End Blocks Id System
/dev/sdb1 1 3547 28491246 7 HPFS/NTFS
/dev/sdb2 * 3548 3573 204800 83 Linux
/dev/sdb3 3573 9964 51339752+ 8e Linux LVM
Disk /dev/dm-0: 50.6 GB, 50591694848 bytes
255 heads, 63 sectors/track, 6150 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 1979 MB, 1979711488 bytes
255 heads, 63 sectors/track, 240 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
[root@server1 ~]# cat /boot/grub/menu.lst
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,1)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_server1-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,1)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.31.6-166.fc12.i686)
root (hd1,1)
kernel /vmlinuz-2.6.31.6-166.fc12.i686 ro root=/dev/mapper/vg_server1-lv_root noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.6-166.fc12.i686.img
title Fedora (2.6.31.5-127.fc12.i686)
root (hd1,1)
kernel /vmlinuz-2.6.31.5-127.fc12.i686 ro root=/dev/mapper/vg_server1-lv_root noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.5-127.fc12.i686.img
title Windows
rootnoverify (hd1,0)
chainloader +1
[root@server1 ~]#
I am not using sda at this point.
glennzo
17th December 2009, 10:18 AM
[root@server1 ~]# cat /boot/grub/menu.lst
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,1)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_server1-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,1)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.31.6-166.fc12.i686)
root (hd1,1)
kernel /vmlinuz-2.6.31.6-166.fc12.i686 ro root=/dev/mapper/vg_server1-lv_root noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.6-166.fc12.i686.img
title Fedora (2.6.31.5-127.fc12.i686)
root (hd1,1)
kernel /vmlinuz-2.6.31.5-127.fc12.i686 ro root=/dev/mapper/vg_server1-lv_root noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.5-127.fc12.i686.img
title Windows
rootnoverify (hd1,0)
chainloader +1
[root@server1 ~]#
I am not using sda at this point.
Try this change and see if Windows boots, assuming that /dev/sda is not disconnected from the system board.
title Windows
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,0)
chainloader +1
Additionally, there is a thread here, http://forums.fedoraforum.org/showthread.php?t=236689, about dual booting. Slowjet, a very knowledgable member here, suggests a slightly different way of handling drive mapping. He's probably a lot more accurate than I so if what I've suggested doesn't work try using his method which includes makeactive and boot.
lemtree
17th December 2009, 10:34 AM
I tried your amendment and I get Error 13 when I chose to boot Windows.
I will follow the link you provided.
Thank you.
jbkt23
17th December 2009, 04:21 PM
title Windows
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,0)
chainloader +1
Try this simple change to your lines
title Windows
rootnoverify (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1
Note that on the rootnoverify line I changed hd0 to hd1 which is where windows should show up. This worked for me in the past.
lemtree
18th December 2009, 08:37 AM
Thanks that did the trick.
JK3MP
18th December 2009, 08:59 AM
Note that most computers windows is on hd1 b/c hd0 is usually the factory image and/or restore partition. =) Glad to hear you fixed your issue.
jbkt23
18th December 2009, 05:35 PM
Thanks lemtree for letting us know it worked.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.