The "older" kernel , 2.4.21-4.EL, is running just fine. Click Here to receive this Complete Guide absolutely free. So fara so good. After that, move to other items, like filesystem checks, hardware components, etc. have a peek at these guys
The problem will usually manifest after kernel upgrades. All is booting fine on the old computer. The other two files are the same: -rw-r--r-- 1 root root 1236945 Oct 3 2003 vmlinuz-2.4.21-4.EL -rw-r--r-- 1 root root 1252573 Apr 15 21:34 vmlinuz-2.4.21-32.EL Any ideas? I hope this article sheds some light on your woes.
Doing a quick Google search led me to link 1, link 2, link 3 Following is the excerpt from a link referred to by one of the links above: Most likely This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd1,4) # kernel /vmlinuz-version ro root=/dev/sdb6 # initrd /initrd-version.img #boot=/dev/sda default=6 timeout=10 splashimage=(hd1,4)/grub/splash.xpm.gz title Fedora Ran in to an unrelated install bug, though one with a workaround, so it'll take a while longer to know if uppgradeing will fix it. When you are booted with one kernel, it might list your disks as being /dev/sda whereas your (configured) kernel is expecting it to be /dev/hda.
My new PC has 2 250Gb SATA drives + 1 160Gb portable PATA hd. If it doesn't, it is most likely because the kernel doesn't know the device to begin with (so it can't attempt to display partitions). But maybe it's not removing enough? Vfs Cannot Open Root Device Redhat Whatever strings are passed to the Kdump kernel are bad and interfere with the loading.
However, during the Kdump kernel startup, a panic message appears on the console. Please Append A Correct Root= Boot Option The partitions were also resized to take advantage of the increased disc-space. If I don't get this Kernel to work, how can I remove it as the default and stick to the older one? 11.10 kernel share|improve this question edited Feb 26 '12 Try running the following lscpi command, and paste its output on http://kmuto.jp/debian/hcl/.
Your best bet is to proceed slowly and use a checklist. Please Append A Correct Root= Boot Option Here Are The Available Partitions Why do some banks have more than one routing number in the US? Thanks, Shibu John. Distribution: Fedora 7 Posts: 65 Rep: FC2; VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) I haven't managed to find a solution to this.
kudzu could prolly fix it for me, but it's waiting for a keyboard press to activate Anyway, I'll com back and open an other thread, should I not be able to Conclusion The VFS error boils down to two things: Kdump command line and initrd modules. Vfs Cannot Open Root Device Or Unknown-block(0 0) My old PC has 1 120Gb Hd with win and 1 30 Gb hd with linux (both PATA). Vfs Cannot Open Root Device Please Append A Correct Root Boot Option 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.
cat /proc/partitions for anyone interested: Code: major minor #blocks name 7 0 73420 loop0 8 0 244198584 sda 8 1 5186128 sda1 8 2 239009400 sda2 8 16 244198584 sdb 8 More about the author Pay special attention to items like mem, memmap and others, which hardcode memory allocations. Solution is here: https://bugzilla.redhat.com/bugzilla....cgi?id=126953 Quote: Additional Comment #1 From C.Laurence Gonsalves on 2004-06-30 14:50 ------- It looks like the problem was due to the initrd being incomplete. Avi for his ideas and help with this thingie! Vfs Cannot Open Root Device Centos
So what gives? Not the answer you're looking for? You will notice I am not giving you any specific instructions, because every system is different. http://ibuildsystem.com/cannot-open/vfs-cannot-open-root-device-label-or-unknown-block0-0.php Let's see them here: VFS: Cannot open root device "LABEL=/" or 00:00 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 00:00 Or the
Ionexchange View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Ionexchange 12-24-2005, 07:52 AM #11 InspectorClusea LQ Newbie Registered: Mar 2004 Distribution: Cannot Open Root Device Mapper/volgroup-lv_root Password Forgot Password? I've seen different people getting this or a similar error, but for different reasons.
Within the menuconfig, you can type "/" to open the search function, and type in the driver name to find out where it resides. # lspci -n Check if you have The "older" kernel , 2.4.21-4.EL, is running just fine. Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. Vfs Cannot Open Root Device Mapper I guess I'll stick with ext3 from now on.
Distribution: Fedora 7 Posts: 65 Original Poster Rep: Hi root partition is /dev/sdb6 ,ie, it's the partition directly after the boot partition. I'm also considering upgrading to FC3, hoping that that might kill the problem. I had a faulty CD-Rom, removing that everything worked fine! –lucacerone Mar 13 '12 at 17:36 add a comment| up vote 0 down vote After reading this answer which explains what http://ibuildsystem.com/cannot-open/vfs-cannot-open-root-device.php It can be sdb4, sdc6 or something else.
RAMDISK: Compressed image found at block 0 Freeing initrd memory: 162k freed VFS: Mounted root (ext2 filesystem). Last edited by Starchild; 12-25-2004 at 09:29 AM. I've put the background info a bit further down. Home Search Login Register Linux Forums - Linux Help,Advice & support community:LinuxSolved.com » Linux in General » Linux Kernel » VFS:cannot open root device "LABEL=/" or 00:00 « previous next »
This is the kernal boot options in my pc. Normally, basic drivers for hardware initialization are included in the initrd image. share|improve this answer answered Sep 30 '13 at 12:25 madcap66 1 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign