In particular, I think it was missing the ata_piix module. Edit your new VM Try a quick Boot Once the import process is complete, go ahead and try powering the system on. Having done that, there are a few files to edit, and then we'll re-create the boot image with the updated settings: Edit the files Edit the following three files and replace It is perfectly ok to point grub to a kernel on (hd0,0) and tell the kernel that you mean sdb for root. http://sauvblog.com/cannot-open/cannot-open-root-device-label.html
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. I have successfuly got kernal 2.4.20-8 to run. Distribution: Fedora 7 Posts: 65 Original Poster Rep: Fixed! If you want more information on it, it's described here. http://www.linuxquestions.org/questions/fedora-35/fc2%3B-vfs-cannot-open-root-device-label%3D-or-unknown-block-0-0-a-269230/
Note that you'll want to make sure that Grub boots to that version when you reboot your VM. VFS: Cannot open root device "LABEL=/" or 00:00 Pleas append a correct "root=" boot option Kernal panic: VFS :Unable to mount root fs on 00:00 Try change "LABEL=/" to "/dev/hda0" (note And I see haven't added sdc yet either.
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 Thanx in advance! I'm also considering upgrading to FC3, hoping that that might kill the problem. Vfs Cannot Open Root Device Redhat It's reiserfs.
Once you've got the steps, it's quite simple, and relatively quick. Please Append A Correct Root= Boot Option That's what you want. Fixing Unix is better than working with Windows. http://forums.fedoraforum.org/showthread.php?t=217140 I went back to my old kernel and the problem went away, but every attempt to use any new kernel failed in the same way.
Tanks very much!ReplyDeleteAdd commentLoad more... Please Append A Correct Root= Boot Option Here Are The Available Partitions Let's nip that before it comes up: echo "DMRAID=no" > /etc/sysconfig/mkinitrd/noraid chmod 755 /etc/sysconfig/mkinitrd/noraid In short, the bug makes this happen when you run mkinitrd: No module dm-mem-cache found for kernel FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc. The best I can offer at this point is to power off the system and change the scsi controller to whatever it isn't set to right now.
Run mkinitrd Simply run mkinitrd -v -f followed by the /boot/initrd-*.img filename and then the kernel version that you noted from /etc/grub.conf above. http://grokbase.com/t/centos/centos/0548zmywpd/cannot-open-root-device-label-on-00-00 Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 09-25-2005, 01:59 AM #10 Ionexchange LQ Newbie Registered: Apr 2004 Location: Vfs Cannot Open Root Device Or Unknown-block(0 0) grub.conf: Code: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option Count trailing truths Why does the Minus World exist?
Several reasons can result in such a failure: the kernel configuration is missing drivers for your HDD controller (cases 1, 4, 5) the kernel configuration is missing drivers for the bus http://sauvblog.com/cannot-open/cannot-open-root-device-label-or-unknown-block0-0.html Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 12-22-2004, 04:22 PM #2 masand LQ Guru Registered: May 2003 Location: 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. VMWare says either will work, but I've had much better luck with LSI. Vfs Cannot Open Root Device Centos
This is what we'll be using. 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 it may also say something Change the VM SCSI controller type Set your VM SCSI controller to use LSI Logic instead of BusLogic. have a peek here To start viewing messages, select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. ** Linuxforums now
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 Cannot Open Root Device Mapper/volgroup-lv_root I know: it was obvious to you; I'm just slow. Thanks, Shibu John.
I reinstalled using the ext3 file system and now have no problem with the UDF-fs: No partition found error or the NVidia driver. up vote 7 down vote favorite 3 whenever I try to boot with linux kernel 184.108.40.206 (the one installed by the upgrades) I get a Kernel Panic error: VFS: Cannot open 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 Please Append A Correct Root= Boot Option Redhat Why does low frequency RFID have a short read range?
how do i do that? Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost timeSubject AscendingDescending Post Reply Print view 16 posts 1 2 Next Return to “CentOS This coused the conversion process to fail at 2% with a generic "Unknown" error until I finally found some info on VMWare's site that indicated the problem was DNS. Check This Out Thanks, too, for the heads-up about the DHCP piece.
Also: I find that the ext3 file system works every bit as fast and good as the reiser file system. 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. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. I was able to follow the instructions and it worked great for me.
In grub.conf, root (hd...) refers to the location of the grub setup, not the location of the root filesystem. Now my system boots up as it should! notageek View Public Profile Find all posts by notageek Tags 0000, device, kernal, label, open, panic, root, vfs « Previous Thread | Next Thread » Thread Tools Show Printable Version Display Is there something I should have compiled that involves the root filesystem that I forgot.
So here's what you do: when the system boots, choose to edit the network settings manually (if you've already gotten past that point, you can edit them from the Network Settings If there is nothing mounted there, you have a problem. Say your root file system uses btrfs (which I definitely don't recommend) but you didn't select it, or selected it to be built as a module, then you'll get the error Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 12-25-2004, 05:36 AM #6 Starchild Member Registered: Sep 2003 Location: At
Help answer threads with 0 replies. Registration is quick, simple and absolutely free. LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora FC2; VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) User Name Remember Me?