My story is this: I've been using the reiser file system for years and have been very happy with it and have kept up with new releases as they were available. 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 It wasn't initially configured to use DHCP for DNS. fstab is also updated to reflect the new hd layout. have a peek at this web-site
E.g.,rpm -ev --nodeps grub-0.97-16.1Reinstall the grub package. If it does, it might help you identify if you misselected a partition (in the example given at the beginning of this section, only two partitions are found whereas the kernel There are a variety of tools out there that are free, and I may get around to exploring those for this situation, as well. Why is looping over find's output bad practice? http://askubuntu.com/questions/71332/kernel-panics-with-cannot-open-root-device-error-where-do-i-append-the-root
Burn that CD, and we'll move on to the next step. Here's the problem: VMWare simply took their Windows-only converter application and put it on a Windows PE boot disk. Check if you have built in (and not as a module) support for the HDD controller you use.
Someone peeled an American flag sticker off of my truck. initrd-2.4.21-47.0.1.EL.img vmlinux-2.4.21-27.0.2.EL config-2.4.21-20.0.1.EL initrd-2.4.21-47.0.1.ELsmp.img vmlinux-2.4.21-27.0.2.ELsmp config-2.4.21-20.0.1.ELsmp initrd-2.4.21-47.0.1.ELsmp.VMWARE.img vmlinux-2.4.21-27.EL config-2.4.21-20.EL initrd-2.4.21-4.EL.img vmlinux-2.4.21-27.ELsmp config-2.4.21-20.ELsmp initrd-2.4.21-4.EL_old.img vmlinux-2.4.21-32.0.1.EL config-2.4.21-27.0.2.EL initrd-2.4.21-4.ELsmp.img vmlinux-2.4.21-32.0.1.ELsmp config-2.4.21-27.0.2.ELsmp initrd-2.4.21-4.ELsmp_old.img vmlinux-2.4.21-37.EL config-2.4.21-27.EL kernel.h vmlinux-2.4.21-37.ELsmp config-2.4.21-27.ELsmp lost+found vmlinux-2.4.21-40.EL config-2.4.21-32.0.1.EL message vmlinux-2.4.21-40.ELsmp config-2.4.21-32.0.1.ELsmp message.ja not foundProbable cause:The initial RAM disk image lacks EVMS support.Resolution:Boot the rescue system and enter the shell. Vfs Cannot Open Root Device Redhat At least, it doesn't do it well with all network cards.
However, that root command above kernel, root (hd1,4), is used by grub to find the boot partition. Please Append A Correct Root= Boot Option For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. Thanks again!ReplyDeleteLaneSeptember 10, 2009 at 12:46 PMDarkman, thanks for the feedback; I'm glad it was helpful! It is perfectly ok to point grub to a kernel on (hd0,0) and tell the kernel that you mean sdb for root.
At Welcome screen, Installation should be selected in place of Boot from Hard Disk. Please Append A Correct Root= Boot Option Here Are The Available Partitions This is what we'll be using. Identify the installed version of GRUB:rpm -q grubRemove the installed version. One issue I did have though was with the network settings for the VMWare Converter.
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 https://access.redhat.com/solutions/1592113 Many mount-related errors are seen during boot.Error(s):Mostly mount-related error messages are seen during boot.startproc: mount returned not-zero exit statusstartproc: /proc not mounted, failed to mount: No such file or directory failedProbable Vfs Cannot Open Root Device Or Unknown-block(0 0) The kernel image is relative to this path. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option Join our community today!
Last edited by Starchild; 12-25-2004 at 09:29 AM. http://rss4medics.com/cannot-open/rms-cannot-open-backup-device.php Also, recent kernels give an overview of the partitions they found on the device told. This site is not affiliated with Linus Torvalds or The Open Group in any way. Then one day I compiled a new kernel and got the UDF-fs: No partition found error. Vfs Cannot Open Root Device Centos
Distribution: Fedora 7 Posts: 65 Original Poster Rep: Hi root partition is /dev/sdb6 ,ie, it's the partition directly after the boot partition. Accept the License Agreement(s) (if prompted).At the Installation Mode screen, select Repair Installed System. Distribution: Fedora 7 Posts: 65 Original Poster Rep: Well, thanx for your help and effort. Source Accept the License Agreement(s) (if prompted).At the Installation Mode screen, select Boot Installed System.
Red Hat Account Number: Red Hat Account Account Details Newsletter and Contact Preferences User Management Account Maintenance Customer Portal My Profile Notifications Help For your security, if you’re on a public Cannot Open Root Device Mapper/volgroup-lv_root 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. This isn't as stupid as it sounds.
All is booting fine on the old computer. So.. I'll note that, if your import process is taking a *really* long time, and failing often during the process, this is most likely your problem. Please Append A Correct Root= Boot Option Redhat Check if the kernel that is being boot by the boot loader is the correct kernel.
Thanks, David /proc/partitions: major minor #blocks name rio rmerge rsect ruse wio wmerge wsect wuse running use aveq 8 0 71557120 sda 690099 3154911 30171650 3230150 87511 165470 2035738 1116540 0 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 UNIX is a registered trademark of The Open Group. have a peek here You may have to register before you can post: click the register link above to proceed.
Find More Posts by masand 12-22-2004, 04:30 PM #3 Starchild Member Registered: Sep 2003 Location: At a tea party with Alice in Wonderland. Bookmark Email Document Printer Friendly Favorite Rating: Troubleshooting Common Boot IssuesThis document (3864925) is provided subject to the disclaimer at the end of this document. Login as root. centos grub2 vfs share|improve this question asked Aug 10 '14 at 8:06 MKroeders 1114 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted Well I
The main difference I observe is that up to 126.96.36.199, the grub conf tries to identify the hard disk using its UUID, 188.8.131.52 now uses /dev/sda6 .. Generally speaking one can say that, if the first digit is 0, then the kernel is unable to identify the hardware. Then I finally narrowed it down to the filesystem. I went to rescue mode and do vim /boot/grub/device.map and 1 line appears (fd0) /dev/fd0 (nothing more).
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 This is where you log in (see: I told you it wasn't free). Create the new Boot Image Now we're (almost) ready to create our new boot image. I tried everything to resolve this problem and searched the web for an answer with no luck.
Last edited by Starchild; 12-25-2004 at 03:07 PM. 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). 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 Comparing the output of fdisk -l may provide additional guidance for the non-existent device. [CTRL]+[D] reboots.Symptom:The system simply hangs after POST.
Last edited by Starchild; 12-22-2004 at 05:04 PM. Now, since we're using LSI Logic for our SCSI controller, we'll add (usually; if the settings are in there, make sure their values are correct) the following: alias scsi_hostadapter mptbase alias