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: 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. Originally Posted by nhasan 1. Adv Reply December 10th, 2011 #7 MAFoElffen View Profile View Forum Posts Private Message Modules & Layers Join Date Mar 2010 Location USA BeansHidden! http://sauvblog.com/cannot-open/cannot-open-root-device-label.html
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 Update grub configuration option. Password Forgot Password? If it fails you should use the Filesystem Check (Fix forced) option and choose your Linux root partition. http://askubuntu.com/questions/71332/kernel-panics-with-cannot-open-root-device-error-where-do-i-append-the-root
As a result, they copy the kernel to the root file system (/) whereas the boot loader still expects the kernel image to be on the /boot partition. please help me to solve this problem. So.. Update grub configuration option.
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 Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Background I got a new PC. Please Append A Correct Root= Boot Option Here Are The Available Partitions But his problem (I forgot to mention this little detail ) is: Code: VFS: Cannot open root device "sda2" or unknown-block (0,0) Please append a correct "root=" boot option: here are
Restore Grub to the MBR option too. Please Append A Correct Root= Boot Option Distribution: Fedora 7 Posts: 65 Original Poster Rep: Fixed! At installation I have also installed the Virtualization package which installed xen, and made the boot record for xen.I realized that I don't have kernel-xen0 and kernel-xenU as I had in http://www.linuxquestions.org/questions/fedora-35/fc2%3B-vfs-cannot-open-root-device-label%3D-or-unknown-block-0-0-a-269230/ Last Jump to page: Results 1 to 10 of 36 Thread: Ubuntu 11.1 - Kernel panic Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid
Recent Posts Virtualizing Drupal Development Environment with Vagrant, Drush &Co November 13, 2015 GHOST Vulnerability: CVE-2015-0235 January 29, 2015 Create an NPC within World of Warcraft to memorialize the late RobinWilliams Vfs Cannot Open Root Device Centos Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Installation & Upgrades [SOLVED] Ubuntu 11.1 - Kernel 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 Distribution: Fedora 7 Posts: 65 Original Poster Rep: Thanx, but I actually tried that, out of desperation and tiredness.
Notify me of new posts via email. https://forums.aws.amazon.com/thread.jspa?threadID=132185 Guessing it has a later version of grub as well, not that I've checked. Vfs Cannot Open Root Device Or Unknown-block(0 0) First of all try the: Grub. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option In particular, I think it was missing the ata_piix module.
This is the kernal boot options in my pc. this contact form paralizer Using Fedora 5 2nd March 2007 08:12 AM Cannot open root device "LABEL=/" or 00:00 on 2.4.26 kernel savudin Using Fedora 4 8th June 2004 01:39 AM Current GMT-time: 10:48 The fs support is there. The error says: VFS: Cannot open root device "LABEL=_/" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to Vfs Cannot Open Root Device Redhat
To fix this, I ran the following: mkinitrd --preload=scsi_mod --preload=sd_mod --with=ata_piix \ /boot/initrd.img-2.6.5-sata 2.6.5-1.358 and then I modified my grub parameters in two ways: - I changed the initrd line to Not sure. The kernel images are found and loaded fine, until we need the stuff on root. have a peek here I have tried repairing using the Rescatux and Ubuntu secure remix (boot-repair) and no luck.This started after upgrading to Ubuntu 11.1.
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 Please Append A Correct Root= Boot Option Redhat I know I can compile a working kernel from this source, I've done it before, but now that I am trying to reduce the size of it I keep getting a That's the portable disc, btw.
Try switching hda with sda (and hdb with sdb, and ...). My old PC has 1 120Gb Hd with win and 1 30 Gb hd with linux (both PATA). 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 Cannot Open Root Device Mapper/volgroup-lv_root Check if the kernel parameter for root= is pointing to the correct partition.
I helped flyingfisch, but your's seems a little different ( at least so far). 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 Kmod: failed to exec/sbin/mod probe -S -K ide If it hangs, he can see where it the messages before it hung. Check This Out Then one day I compiled a new kernel and got the UDF-fs: No partition found error.
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. Though I could not resize the root partiton for some reason. I don't see a root option when i select the recovery kernel (just a sparse files message) and press enter to continue - leading up to the messages around the panic root (hd0,2) kernel /boot/vmlinuz-2.4.22-1.2115.nptlsmp ro root=LABEL=/ rhgb initrd /boot/initrd-2.4.22-1.2115.nptlsmp.img I had changed the root device LABEL into "root=/dev/hda2" [and other numbers] then the error came like this..
If it had the forced fix then you could use that instead of Rescatux fsck option. References: http://amazonserver.blogspot.com/2013/01/recover-broken-amazon-ec2-instance.html http://smoove-operator.blogspot.com/2014/01/red-hat-enterprise-linux-server-in.html Share this:TwitterFacebookPrintLinkedInGoogleEmailMoreTumblrPinterestPocketRedditLike this:Like Loading... This forum is for the XenServer family only.You can find the open source Xen mailing lists at the links given below:http://lists.xensource.com/archives/html/xen-users/Regards,Deepak 1345-151507-1006938 Back to top Guest Members #3 Guest 6,766 posts