GRUB2 Kernel Panic Rootfs failing to boot: VFS: unknown-block (0,0)
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I haven't had a problem before with using the NTFS windows boot partition with linux, but it could be that Gentoo has a problem with it.
GRUB even has msdos (ntfs) modules built in. It can't be the filesystem.
The problem is the kernel panic, failing to boot after selecting the GRUB Gentoo kernel. It gives the unable to sync VFS unknown-block(0,0) message and I have to hard shutdown. I googled the message and so far I've tried to verify the grub.cfg is correct, and the HDD controller drivers are loaded.
Last edited by luzion; 07-16-2019 at 10:01 PM.
Reason: adding info here
Well, for starters I'd imagine you haven't even begun to clearly specify the problem you're having here. What is going on? Is your system failing to boot? Are you hanging? What messages are you receiving? Your partition layout is not an error message, it's just a listing of disks. What is the operation you expect or don't expect? At what stage of reboot is it happening?
Secondly -- I'll take a wild guess and say this is your problem here -- NTFS (the default filesystem in Microsoft Windows) should not even be remotely close to selectable for a Linux partitioning scheme, let alone for /boot which is where your kernel resides. You should be using ext4 or heck, even ext2.
Last edited by RickDeckard; 07-11-2019 at 11:21 PM.
you say your boot partition is /dev/sda1, but in grub gentoo menu entry you have
Code:
set=(hd0,3)
linux /boot/vmlinuz root=/dev/sda3
not
Code:
set=(hd0,1)
/vmlinuz root=/dev/sda3
or your missing some obscure driver you system needs loaded.
I changed that parameter to be (0,1). Where could I start in finding if its a missing driver?
Gentoo's manual also recommends for MBR legacy machines like mine that there be a BIOS boot partition for grub from 2048 to +2M, but I followed the guide that mentioned installing Windows first was okay(hence using the windows boot partition), but maybe adding one now could fix it? This would fix what someone else mentioned about Linux not being able to boot on an NTFS partition.
Any suggestions are appreciated as I'm lost here.
It's a bit late in the day, but I would have said "Don't use Gentoo!" It has a lot going for it (bleeding edge software and the most freedom of choice of any distro), but it is definitely for experts only.
As far as the BIOS boot partition is concerned, you need one to accommodate the second stage of GRUB if you have a GPT disk booting from a BIOS. If it's a traditional DOS MBR disk, you don't need one because GRUB Stage 2 will fit into the gap between the MBR and the first partition.
I reread this thread, let see if I got this straight, you get a grub menu, you select the entry you want to boot, up comes a few lines of code, then the message
Quote:
Kernel Panic Rootfs failing to boot: VFS: unknown-block (0,0)
If that is true then has nothing to do with grub. Your most likely missing a kernel driver to boot your system. what are the last several lines displayed on the screen before it locks up? How did you compile the kernel.
Last edited by colorpurple21859; 07-25-2019 at 05:37 AM.
It's a bit late in the day, but I would have said "Don't use Gentoo!" It has a lot going for it (bleeding edge software and the most freedom of choice of any distro), but it is definitely for experts only.
As far as the BIOS boot partition is concerned, you need one to accommodate the second stage of GRUB if you have a GPT disk booting from a BIOS. If it's a traditional DOS MBR disk, you don't need one because GRUB Stage 2 will fit into the gap between the MBR and the first partition.
I appreciate your advice Gentoo is over my head! The handbook listed the example partitioning for BIOS/MBR to include a BIOS boot. I looked at the quick guides and complete guides as well and they confirm that it's not needed.
Quote:
Originally Posted by colorpurple21859
what are the last several lines displayed on the screen before it locks up?
The last lines are "cpu:3 pid: 1 Comm: swapper/0 not tainted 4.19.57-gentoo #2", a call trace, Kernel offset relocation range, and the kernel panic not syncing root fs error. I tried to find the whole output but it was not in /var/log/.
Quote:
Originally Posted by colorpurple21859
How did you compile the kernel.
Manually, using the guide first and safe C/USE flags, then referencing someone else's configuration on a similar machine and emerging* again.
*make
try using genkernel or boot into the medium used to install Gentoo and run lsmod to see what modules are loaded and compare to what you have built in your kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.