kernel panic on reboot of newly compiled kernel

lyceum · 09-09-2003, 02:49 AM

just compiled 2.4.22 and upon rebooting get the following error message:

Code:

VFS:  Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic:  VFS:  Unable to mount root fs on 00:00

here is my 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/hda2
#          initrd /initrd-version.img
#boot=/dev/hda
default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.22)
        root (hd0,0)
        kernel /vmlinuz-2.4.22 ro root=LABEL=/ hdc=ide-scsi
        initrd /initrd-2.4.22.img
title Red Hat Linux (2.4.20-19.23.rh9.at)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-19.23.rh9.at ro root=LABEL=/ hdc=ide-scsi
        initrd /initrd-2.4.20-19.23.rh9.at.img
title Red Hat Linux (2.4.20-6)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-6 ro root=LABEL=/ hdc=ide-scsi
        initrd /initrd-2.4.20-6.img

i have no problems booting into the two other kernel versions listed here.

Can anyone help me with this? Thanks in advance.

NOTE: compiled kernel according to Drozz's guide found here:
http://www.linuxquestions.org/questi...355#post379355

acid_kewpie · 09-09-2003, 03:29 AM

i'd assume that you'd need to specifically enable ext2 label support. or just change the entry to a real /dev/hdXY entry - press e to edit the line etc....

TigerOC · 09-09-2003, 05:14 AM

Interesting as I am also having similar problems with this kernel seehere

Skyline · 09-09-2003, 07:53 AM

Initially - I had a similar error with 2.4.22 on Red Hat 9 with LILO - I sorted it by explicitly stating what the device name of the root partition was - ie - I inserted :

root=/dev/hda3

and got rid of :

root=LABEL=/

from lilo.conf.

h/w · 09-09-2003, 09:40 AM

same here, "/" didnt work and gave me the same error as posted above.
"/dev/hda" worked.