Home > Cannot Open > P2v Cannot Open Root Device

P2v Cannot Open Root Device


Check if you have built in (and not as a module) support for the bus / protocol that your harddisk controller uses. I used the following process to migrate these machines. 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 What do I do? http://amigasuperbit.com/cannot-open/qemu-cannot-open-root-device-nfs.html

Make sure the file system support is built in the kernel. Thanks again!ReplyDeleteLaneSeptember 10, 2009 at 12:46 PMDarkman, thanks for the feedback; I'm glad it was helpful! Non-Repetitive Quine Do the Leaves of Lórien brooches have any special significance or attributes? 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 http://askubuntu.com/questions/71332/kernel-panics-with-cannot-open-root-device-error-where-do-i-append-the-root

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

Password Fedora This forum is for the discussion of the Fedora Project. Home Forum Today's Posts | FAQ | Calendar | Community Groups | Forum Actions Mark Forums Read | Quick Links View Site Leaders | Unanswered Posts | Forum Rules Articles Marketplace Find More Posts by masand 12-25-2004, 08:26 AM #8 Starchild Member Registered: Sep 2003 Location: At a tea party with Alice in Wonderland. I notice that after the computer probes for IDE interfaces it brings up hda and it doesn't know what fs it is.

The fs support is there. I've put the background info a bit further down. I reset the system and somehow we got a third option in the GRUB which did work (magic) so now the system is running again. Vfs Cannot Open Root Device Redhat See /proc/partitions and fstab below.

I've tried changeing LABEL=/ to /dev/sda5 (which I *think* is my root drive..) but no luck. Please Append A Correct Root= Boot Option 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. The message occurs during boot-up right after Loading jdb.ko module Loading ext3.ko module Creating block devices curiously (to me) is that a few lines up we have: VFS: Mounted root (ext2 https://kb.vmware.com/kb/1004576 Having done so, you'll see a link to download VMware vCenter Converter BootCD for vCenter Server.

Accept the License Agreement(s) (if prompted).At the Installation Mode screen, select Boot Installed System. Please Append A Correct Root= Boot Option Here Are The Available Partitions Thanx in advance! 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. 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.

Please Append A Correct Root= Boot Option

Verify the existence of /boot/grub/menu.lst.If existing, but misnamed, rename it.If corrupt, delete it and Repair Installed System** (just the Boot Loader Configuration check should be sufficient).If missing, Repair Installed System** (just https://access.redhat.com/solutions/1592113 If not, you're done. Vfs Cannot Open Root Device Or Unknown-block(0 0) Registration is quick, simple and absolutely free. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option So enough of the fine print: let's get to it.

I did a fdisk -l; But there ends the train for me, unfortunately. Check This Out We Acted. 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: 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 Centos

That's what you want. This also fixed a problem with compiling the NVidia graphics driver. UbuntuCommunityAsk!DeveloperDesignDiscourseHardwareInsightsJujuShopMore ›AppsHelpForumLaunchpadMAASCanonical current community chat Ask Ubuntu Ask Ubuntu Meta your communities Sign up or log in to customize your list. Source Ok solved the problem!

It is perfectly ok to point grub to a kernel on (hd0,0) and tell the kernel that you mean sdb for root. Cannot Open Root Device Mapper/volgroup-lv_root A story behind a weird inductor Can I substitute decaf coffee for espresso Teenage daughter refusing to go to school Is there a word for being sad about knowing that the Manually mount the root filesystem (i.e., mount /dev/sda2 /mnt).

It was originally created with PQ:s Partition Magic 8.0, but that program can't resize it either.

Select the desired Language. Thanks for leaving a comment! Is it possible that it is a SCSI problem? Please Append A Correct Root= Boot Option Redhat 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.

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 Why were pre-election polls and forecast models so wrong about Donald Trump? You are currently viewing LQ as a guest. have a peek here Last edited by Starchild; 12-25-2004 at 03:07 PM.

Though I could not resize the root partiton for some reason. 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 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 Someone peeled an American flag sticker off of my truck.

My cat sat on my laptop, now the right side of my keyboard types the wrong characters GO OUT AND VOTE Can a text in Latin be understood by an educated You most likely don't, so here's a quick check-up. If not, comparing its output with the contents of /etc/fstab should. This will make things work much, much better.

There is one very important gotcha, however: Network Autonegotiation Speed. Run manually!fsck failed for at least one filesystem (not /).Probable cause:Invalid/etc/fstabentry, /dev/hdb3 is a non-existent device.Resolution:Enter the root password to enter maintenance mode. That drive no longer exists: it's been converted to a SCSI disk, so we need to tell Linux how to read its new disk. In my case, it looked like this: mkinitrd -v -f /boot/initrd-2.6.18-92.1.1.el5.img 2.6.18-92.1.1.el5 When that runs to completion, you should be able to boot.

Check if you have built in (and not as a module) support for the HDD controller you use. It wasn't initially configured to use DHCP for DNS. So fara so good. Why is looping over find's output bad practice?

If you need to reset your password, click here. up vote 7 down vote favorite 3 whenever I try to boot with linux kernel (the one installed by the upgrades) I get a Kernel Panic error: VFS: Cannot open