kernel panic - not syncing : VFS: unable to mount root FS on unknown-block
SlackwareThis Forum is for the discussion of Slackware Linux.
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 - not syncing : VFS: unable to mount root FS on unknown-block
I'm geting this error message at startup:
"kernel panic - not syncing : VFS: unable to mount root FS on unknown-block"
I just upgraded from kernel 2.4 to 2.6, then this happend.
any suggestions?
Same thing happened to me when I didn't include reiser support in the kernel. You can either include the filesystem support in your kernel or create an initrd to load the module at startup.
Do a search on the error message to find other suggestions.
I'm and idiot!! The problem was in lilo, i asumed that my loader was pointing to hda3; when in reality it was pointing to hda1
Thanks for your timely help!
I have the same problem(I upgraded to 2.6.13)
but I'm pretty sure that I included my ide and filesystem statically(not modules) (I already compiled my own kernel before), and I'm also sure that there is nothing wrong about my lilo.conf because "make install" does that automatically(I also checked my self)
Hi guys,
I went through the same problem when I upgraded kernel from 2.4 to 2.6 on Dell Inspiron 6000 laptop. It is documented here. And specifically, the fix post
What IDE controller do you have? Or specifically what is the chipset?
There is a likely hood that on 2.6 kernel, your IDE harddisk is recognise as /dev/sd**, just as it happens to mine.
The solution is to change the lilo.conf entry for your new kernel image root = /dev/sd**
Remember to change your /etc/fstab entries as well. If you do not change that, you will be able to boot but the kernel will complain it can't mount the root partition later.
Last edited by carboncopy; 10-19-2005 at 08:11 AM.
I got the same problem here, my SuSE 9.2 can't boot. I understand that I must reach config file but I can not even reach my HD with external tools, such as this famous Ultimate Boot CD which includes a live Linux too. The hda1 (swap) and hda2 (reiserfs) are seen in the table of Qtparted (a GUI tool for handling partitions) but hell, no way to change anyting on them, formatting doesn't work either. The booting stops with the error message: hda: read-initr: uncorrectable error: LBA 2020108 This sector is in the hda2 partition that includes SuSE 9.2. Any workaround for that?
Hello Experts,
I am having same problem after I upgraded my Ubuntu.
Ubuntu is installed as application on my XP.
Normal Ubuntu gives me error "[ 0.785649] kernel panic - not syncing : VFS: unable to mount root FS on unknown-block(8,2)"
Safe/Recovering boot option gives me details traceback..
Pid :1 comm: swapper not tainted 2.6.32-27-generic#
call Trace:
[<c058b313>]?printK+0x1d/0x22
....
Please need a help..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.