Red HatThis forum is for the discussion of Red Hat 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.
But it will not boot, it says:
VFS: Cannot Open Root Device "Label=/" or unknown-block(0,0) Please append a correct "root=/" boot option
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I tried using /dev/sda1 instead of Label=/, and I have the ext3 file system built in(not as a module), I also tried increasing the ramdisk size.
How do I get it to boot? Did anyone else get those errors?
I just wanted to reply that I had the same or similiar problem. My fault was not in lilo (or in your case, grub) because the 2.4.22 kernel was booting, but my 2.6.11.7 kernel was not. Even though they were given the SAME information in lilo.conf . Going with this knowledge I determined that it was saying "unknown-block" because it did not recognize the disk (in my case it was a scsi disk) The 2.4.22 kernel had all SCSI device drivers enabled as Modules. But in my 2.6.11.7 kernel config, I had forgotten about my scsi drivers. I needed AHA-7xxx support to run my adaptec 29160n pci controller and therefore be able to use my scsi disks where my root partition was located. So I changed my kernel config to use the scsi drivers and HUZZAH it worked. So in short, be sure you have the correct block device drivers enabled. If you are unsure, enable it as a Module just to be safe. Be sure if you are using scsi disks to enable the corresponding controller. If you are using IDE (majority say yes here) be sure it is enabled. With IDE it should be enabled by default though...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.