Grub question

TurboChicken · 03-06-2006, 10:14 AM

Code:

# 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/hde
default=0
timeout=5
splashimage=(hd0,1)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11-1.1369_FC4)
        root (hd0,1)
        kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.11-1.1369_FC4.img
title Other
        rootnoverify (hd2,0)
        chainloader +1

when i try and boot into windows it gives me nothing...

all i see on the screen is:

Code:

        rootnoverify (hd2,0)
        chainloader +1

windows is installed on hde5 so the hd2,0 doesn't seem right to me...

is there something wrong??

it has worked before now... but i don't know what's gone wrong???

acid_kewpie · 03-06-2006, 10:42 AM

hd2,0 in grub is hdc1 inside linux, so you presumably what to use (hd3,4) instead. you can always use the e key to edit the line temporarily within grub.

TurboChicken · 03-06-2006, 06:08 PM

i fixed it... but it seems to be relative to the partition that grub is on... the correct line was hd0,0

jiml8 · 03-06-2006, 06:15 PM

You need to study device.map to figure out how grub is mapping the drives.

grym · 03-07-2006, 12:00 AM

If windows wasn't booting I think grub was working great

You don't need a device map necessarily. Grub has command-line completion just like bash. So you could type something like --

root (

then hit tab and it will provide you with the available options. Also grub doesn't care whether a drive is IDE, SCSI, or SATA - they all start with hd0 and go up from there.