grub.conf isn't being read; I'm being thrown into a grub command prompt each time

punt · 05-30-2011, 08:51 PM

Does anyone have a clue why my grub.conf doesn't seem to be read? See subject for full details

grub.conf is the same as menu.lst. It's a symlink. I also have /etc/grub.conf but it's also a symlink to the /boot/grub/grub.conf file.

I'm very confused, since I upgraded to Fedora 15 and ran

Code:

/sbin/grub-install BOOTDEVICE

properly, specifying the correct location for the BOOTDEVICE, and for some reason it's not working.

TIA!

RockDoctor · 05-31-2011, 08:03 AM

Where did you install grub, and what does your grub.conf file look like? Here's a representative section of mine (located on /dev/sda3):

Code:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,11)
#          kernel /boot/vmlinuz-version ro root=/dev/sda12
#          initrd /boot/initrd-[generic-]version.img
#boot=/dev/sda25
timeout=65
splashimage=(hd0,2)/boot/grub/splash.xpm.gz
#hiddenmenu

title Fedora 15-64 (Lovelock) sda5
	rootnoverify (hd0,4)
	chainloader +1
	

title -----------------------------------------
root 

title Windows 7 sda1 & sda10
	rootnoverify (hd0,0)
	chainloader +1

punt · 05-31-2011, 09:52 AM

I installed to the correct locations. /dev/sda - no errors.

My old grub.conf (which I backed up) is the same as my new grub.conf.

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,0)
#          kernel /vmlinuz-version ro root=/dev/sda3
#          initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=0
#splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
#title Fedora (2.6.38.6-27.fc15.i686)
#       root (hd0,0)
#       kernel /vmlinuz-2.6.38.6-27.fc15.i686 ro root=UUID=fcbb756b-c2c2-496d-99fd-eb32ab510973 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
#       initrd /initramfs-2.6.38.6-27.fc15.i686.img
title Fedora (2.6.35.13-91.fc14.i686)
        root (hd0,0)
        kernel /vmlinuz-2.6.35.13-91.fc14.i686 ro root=UUID=fcbb756b-c2c2-496d-99fd-eb32ab510973 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
        initrd /initramfs-2.6.35.13-91.fc14.i686.img
title Fedora (2.6.35.12-88.fc14.i686)
        root (hd0,0)
        kernel /vmlinuz-2.6.35.12-88.fc14.i686 ro root=UUID=fcbb756b-c2c2-496d-99fd-eb32ab510973 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
        initrd /initramfs-2.6.35.12-88.fc14.i686.img
title Fedora (2.6.33.6-147.fc13.i686)
        root (hd0,0)
        kernel /vmlinuz-2.6.33.6-147.fc13.i686 ro root=UUID=fcbb756b-c2c2-496d-99fd-eb32ab510973 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
        initrd /initramfs-2.6.33.6-147.fc13.i686.img

FWIW, this issue is not solved but I reinstalled Fedora and now don't encounter the issue anymore. My woes are now inittab related

RockDoctor · 05-31-2011, 04:56 PM

Running F15, inittab shouldn't be a problem (famous last words) unless you're not using systemd.