Home > Cannot Open > Vfs Cannot Open Root Device Label

Vfs Cannot Open Root Device Label

Contents

Distribution: Fedora 7 Posts: 65 Original Poster Rep: Well, thanx for your help and effort. Before you can solve the problem, you need to understand what it is. This isn't as stupid as it sounds. Red Hat nash version 3.5.14 starting Loading jbd.o module Journalled Block Device driver loaded Loading ext3.o module Mounting /proc filesystem Creating block devices VFS: Cannot open root device "LABEL=/" or 00:00 weblink

shibujohn View Public Profile Find all posts by shibujohn #2 18th March 2009, 03:57 PM notageek Offline Registered User Join Date: Jan 2008 Location: N/A Posts: 2,148 All Thread Tools Search this Thread Display Modes #1 17th March 2009, 11:16 AM shibujohn Offline Registered User Join Date: Mar 2009 Posts: 1 Kernal panic VFS cannot open After you make the changes, recreate the initrd image. /sbin/mkinitrd On some systems, initrd may also be named initramfs under /boot, so don't panic if you see a different naming convention. 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.

Vfs Cannot Open Root Device Or Unknown-block(0 0)

Last edited by Starchild; 12-25-2004 at 09:29 AM. We talked about this in the Ubuntu initrd saga. Ok solved the problem! The "older" kernel , 2.4.21-4.EL, is running just fine.

The basic principle remains the same. Also: I find that the ext3 file system works every bit as fast and good as the reiser file system. it sound like this might be an initrd issue if the older kernel works fine. Vfs Cannot Open Root Device Redhat It can be sdb4, sdc6 or something else.

Here's an example: cat /proc/iomem 00000000-0009dbff : System RAM 0009dc00-0009ffff : reserved 000a0000-000bffff : Video RAM area 000c0000-000cafff : Video ROM 000f0000-000fffff : System ROM 00100000-bf61ffff : System RAM 00100000-002f684d : Please Append A Correct Root= Boot Option Most likely this is PCI support, SATA support (which is beneath SCSI device support), ... when GRUB is running it doesn't recognize the jaz drive as it is currently disabled as a boot device although I have booted from the jaz in the past - the The problem here is that the kernel that you are booting cannot translate the root=/dev/...

How do I make an alien technology feel alien? Please Append A Correct Root= Boot Option Here Are The Available Partitions I hope this article sheds some light on your woes. It seems that when you compile a new kernel, the reiser file system will not access the hard drive without some manipulation with the reiserfs tools. And also the one mentioned in the error msg.

Please Append A Correct Root= Boot Option

It is perfectly ok to point grub to a kernel on (hd0,0) and tell the kernel that you mean sdb for root. First, see whether the problem can be worked around by changes to the kernel command line or the initrd configuration. Vfs Cannot Open Root Device Or Unknown-block(0 0) The "older" kernel , 2.4.21-4.EL, is running just fine. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option Now..

So there appears to be a problem in the way the FC2 installer constructs the initrd that it installs on some systems. http://bovbjerg.net/cannot-open/vfs-cannot-open-root-device-nfs.php Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Join Us! I'm also considering upgrading to FC3, hoping that that might kill the problem. Vfs Cannot Open Root Device Centos

  1. Distribution: Fedora 7 Posts: 65 Original Poster Rep: *hopeful bump* Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 12-25-2004, 07:28
  2. So fara so good.
  3. Ask Ubuntu works best with JavaScript enabled Home Forums Posting Rules Linux Help & Resources Fedora Set-Up Guides Fedora Magazine Ask Fedora Fedora Project Fedora Project Links The Fedora Project Get
  4. So that is as it should be. (Btw setting this to hd1,5 will cause the system to hang much earlier with a different error message, as I have no kernel images
  5. There are two variations to this message and many possible reasons to why it shows up.
  6. Since the new kernel is more up to date, I would much rather try to get the other on working.
  7. Then one day I compiled a new kernel and got the UDF-fs: No partition found error.
  8. FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

For example, you may have special hardware that needs special drivers. Hot Network Questions Single word for the act of being susceptible? Check if you have built in (and not as a module) support for the bus / protocol that your harddisk controller uses. http://bovbjerg.net/cannot-open/vfs-cannot-open-root-device-label-or-unknown-block0-0.php InspectorClusea View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by InspectorClusea 01-18-2006, 04:39 AM #12 assa9 LQ Newbie Registered: Jan 2006 Posts:

Anyhoo, I tried to uppgrade to FC 3, see if that will solve it. Cannot Open Root Device Mapper/volgroup-lv_root One, the KDUMP_COMMANDLINE directive, as specified in the /etc/sysconfig/kdump configuration file. Visit Jeremy's Blog.

The file system I was using was the new reiser4.

The init script located under /etc/init.d/kdump performs some search & replace changes on the collected string so it is good enough for the Kdump kernel. While some of the items may not be applicable for the Kdump kernel, you will get a pretty good indication if you're trying to do something that conflicts with reserved segments. One of the most frequent cases: you selected support for your harddisk controller protocol (IDE, SATA, SCSI, ...) but forgot to select the HDD controller driver itself (like Intel PIIX). Vfs Cannot Open Root Device Mapper Though, I still have root=LABEL=/ as kernel parameter, not root=/dev/sdb6 Now I have a few other things to fix, as my new keyboard is usb now, not ps/2...

After that, move to other items, like filesystem checks, hardware components, etc. You setup your machines. I've put the background info a bit further down. this content 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

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 So instead of resizing the root partition, I just created a new one (tried merging it with the root partition, but no success ) grub also installed without any problems (well It's reiserfs. Click Here to receive this Complete Guide absolutely free.

Make the necessary changes, like cleaning the kernel command line a little more and/or adding the missing modules. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. How can I solve this? LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora FC2; VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) User Name Remember Me?

Distribution: Fedora 7 Posts: 65 Original Poster Rep: Fixed! Last edited by Starchild; 12-25-2004 at 03:07 PM. Find More Posts by masand 12-23-2004, 04:01 AM #5 Starchild Member Registered: Sep 2003 Location: At a tea party with Alice in Wonderland. The kernel image is relative to this path.

Also, recent kernels give an overview of the partitions they found on the device told. parted says that it has some oddities, that may cause (fixable) problems. Using the eval command twice How good should one be to participate in PS? However, that root command above kernel, root (hd1,4), is used by grub to find the boot partition.

Would you like to advertise your product/site on Dedoimedo? Please visit this page to clear all LQ-related cookies. So what gives? At the very least, you learned a little bit more about systematic problem solving, Kdump command line and init script, memory allocations under /proc, how to edit the kernel configuration, and