Dual Boot into Windows Fails after Yum Updates

Led Zappa · 01-27-2008, 11:17 PM

I created a partition for Centos 5 using parted magic on my windows server system. It worked fine. Then I got a notice that updates were available. After Performing the updates I went from having 3 (1 Windows / 2 Linux) Boot Optoins to 5 (1 Windows / 4 Linux). I can still boot to Centos 5, but it hangs when trying to load Windows Server at:

'Booting Windows Server'
rootnoverify
chd2,4
chainloader +1

Here is my grub.conf and device.map files

Code:

grub.conf 

# 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 (hd0,1)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=4
timeout=5
splashimage=(hd0,1)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-53.1.6.el5xen)
    root (hd0,1)
    kernel /xen.gz-2.6.18-53.1.6.el5
    module /vmlinuz-2.6.18-53.1.6.el5xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    module /initrd-2.6.18-53.1.6.el5xen.img
title CentOS (2.6.18-53.1.6.el5)
    root (hd0,1)
    kernel /vmlinuz-2.6.18-53.1.6.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.18-53.1.6.el5.img
title CentOS (2.6.18-53.el5xen)
    root (hd0,1)
    kernel /xen.gz-2.6.18-53.el5 crashkernel=128M@16M
    module /vmlinuz-2.6.18-53.el5xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    module /initrd-2.6.18-53.el5xen.img
title CentOS-base (2.6.18-53.el5)
    root (hd0,1)
    kernel /vmlinuz-2.6.18-53.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.18-53.el5.img
title Windows Server
    rootnoverify (hd2,4)
    chainloader +1


Device Map File:

# this device map was generated by anaconda
(hd2)     /dev/hda
(hd0)     /dev/sda

Help

I could make some educated guesses, but I don't want to end up not being able to boot to Centos at least.

And why did I end up with all those Linux boot options. Can I get rid of all but 1. I have always selected the first boot option for linux.

ravibhure · 01-27-2008, 11:40 PM

Hi,
I give you silly one answer but you have to check your cable connections of your hard disk. If one of them (IDE-data cable & power cable) that connected your hard disk to motherboard would be loose. Just keep it tight or fix & boot your system again then see whats going with your windows.

Led Zappa · 01-27-2008, 11:46 PM

Quote:

Originally Posted by ravibhure

Hi,
I give you silly one answer but you have to check your cable connections of your hard disk. If one of them (IDE-data cable & power cable) that connected your hard disk to motherboard would be loose. Just keep it tight or fix & boot your system again then see whats going with your windows.

They are both on the same physical disk on 2 partitions and Centos boots fine. Parted Magic made a partition at the end of the disk and Centos made the Linux Partitions automatically during the install. I should have looked at the grub.conf file as soon as I installed the OS so I knew what it looked like. Oh well, too late now.

Led Zappa · 01-28-2008, 12:50 PM

Don't know why nobody helped me with this. I finally booted with get parted and tried to make the most sense I could out of the data.

I changed the Windows line from rootnoverify (hd2,4) to rootnoverify (hd0,0) and it boots to Windows now. How it got changed just by doing the updates is beyond me. I also would like to know why I ended up with 4 Linux Options. Heck I don't even know why I had 2 Linux boot options to begin with.

It would be nice if someone could comment. This is the Newbie forum and I am a Newbie. I am willing to do my own homework, but when it comes to messing around with booting options, I could have wrecked it to the point I couldn't boot at all. Though I feel comfortable getting around Linux because I used to use DOS a lot, this can be very intimidating to a new comer.