Kernel panic: VFS: Unable to mount root fs on 00:00
Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kernel panic: VFS: Unable to mount root fs on 00:00
After updating from redhat network, my system I received the following error:
VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" host option
Kernel panic: VFS: Unable to mount root fs on 00:00
My grub.conf file is:
default=0
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
title Red Hat Enterprise Linux ES (2.4.21-32.EL)
root (hd0,1)
kernel /vmlinuz-2.4.21-32.EL ro root=LABEL=/ hdc=ide-scsi
initrd /initrd-2.4.21-32.EL.img
title Red Hat Enterprise Linux ES (2.4.21-4.EL)
root (hd0,1)
kernel /vmlinuz-2.4.21-4.EL ro root=LABEL=/ hdc=ide-scsi
initrd /initrd-2.4.21-4.EL.img
title XP
rootnoverify (hd0,0)
chainloader +1
As you can see I have two kernels available. The "older" kernel ,
2.4.21-4.EL, is running just fine. Since the new kernel is more up to
date, I would much rather try to get the other on working.
I checked and compared the referenced the img files and here is the
info:
-rw-r--r-- 1 root root 165303 Apr 19 21:58
initrd-2.4.21-4.EL.img
-rw-rw-r-- 1 root root 164452 May 18 15:01
initrd-2.4.21-32.EL.img
and I see that both files are similar except that the new kernel has
an extra "w" in the group.
The other two files are the same:
-rw-r--r-- 1 root root 1236945 Oct 3 2003
vmlinuz-2.4.21-4.EL
It seems like your kernel is not configurated correctly, please make sure that your kenel configuration include devfs option, ext2,ext3, and other required file system, both in built in mode.
I think you need to compile the kernel again.
make sure to make all filesystems(exept for the filesystem of your root partition whitch you need to be compile into the kernel) modules in the configutration.
Hi there,
Check the modules.conf file; if this is buggered when you installed the new kernel, mkinitrd ran and could have left out the disk driver (or it could have changed name) HP used to have a cciss driver that was called cciss_432, this went into the modules.conf file; when the kernel was upgraded the module was called cciss_555 (example numbers) so mkinitrd ran, an insmod cciss_432 was included in lt linuxrc script which now was removed and panic...... Other things are controller orders in modules.conf.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.