Kernel Panic : VFS Unable to mount root fs on 09:02
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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 09:02
Hello,
I just used up2date to get the most recent kernel for redhat 8. When I reboot the computer the boot halts and I'm unable to run even a command line. Here are the last three messages:
*****************************************
EXT2-fs: unable to read superblock
isofs_read_super : bread failed, dev = 09:02, iso_blknum=16, block=32
Kernel Panic : VFS : Unable to mount root fs on 09:02
*****************************************
I'm using a Dell Inspiron 4000 800Mhz, 40GB, 256Meg, BIOS A20.
The machine dual boots w/ Win2K using Paragon bootmanager.
Is there a way to back down to the old kernel? Is there any type of emergency boot mode?
I'm a newbie and really stuck! Any help is greatly appreciated.
This is a common problem and it has only a few causes. First, check the device XX:YY against the list of device codes; is it the correct root device? If not, you probably didn't do an rdev -R, or you did it on the wrong image. If the device code is correct, then check carefully the device drivers compiled into your kernel. Make sure it has floppy disk, ramdisk and ext2 filesystem support built-in.
copied from http://www.csse.uwa.edu.au/programmi...k-HOWTO-7.html
Last edited by arunshivanandan; 10-11-2003 at 05:44 AM.
I've found a temporary solution to this. If I understand correctly, it looks like the boot loader thought the root partion was on a raid device (09:02). Weird. I'm able to boot the new kernel by pressing F2 when booting and manually entering the root parameter:
root=/dev/hda3
Now I just need to figure out where to put this so that I don't have to manually enter it each time. I thought it might be grub.conf, but that doesn't seem to do it and I can't find etc/lilo.conf. Does anyone know how do to this? Am I headed in the right direction?
Also, how can I determine which bootloader the OS is actually using?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.