LFS error: boot lfs, Kernel panic -not syncing:VFS unable to mount root fs on unknown-block(0,0)
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
LFS error: boot lfs, Kernel panic -not syncing:VFS unable to mount root fs on unknown-block(0,0)
After having finished LFS, it is time to boot it ,but druing boot lfs, log show as follows:
"Kernel panic -not syncing:VFS unable to mount root fs on unknown-block(0,0)"
this is our information:
our lfs is built on /dev/sda3.
we boot lfs from grub by using the following command
"grub> linux (hd0, msdos3)/boot/vmlinuz-4.9.9-lfs-8.0-systemd root=/dev/sda3 ro"
grub>boot
"
we use SCSI disk ,but before make kernel, I have checked the menu config about scsi driver, we have add this options.
Besides disk driver, you also need a filesystem driver and scsi generic drivers built into kernel.
Yes, the kernel, using only drivers that are built into it (since you're not using the initrd hack) must contain all of the drivers needed both to communicate with the hardware and to understand the file-system that it will find there.
For convenience, I ordinarily build into the kernel all of the filesystem and hardware drivers that I know that I might encounter, such as FAT32 on your garden-variety USB stick. (Filesystem drivers used for removable devices can also, of course, be modules that will be loaded by hotplug/coldplug on demand ... but they're really not that big, anyhow.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.