Home > Cannot Open > Cannot Open Root Device Label

Cannot Open Root Device Label

Contents

Since the new kernel is more up to date, I would much rather try to get the other on working. Is there something I should have compiled that involves the root filesystem that I forgot. Conclusion The VFS error boils down to two things: Kdump command line and initrd modules. Make sure the file system support is built in the kernel. Source

fstab is also updated to reflect the new hd layout. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 162k freed VFS: Mounted root (ext2 filesystem). Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ Then I finally narrowed it down to the filesystem.

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

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 If I don't get this Kernel to work, how can I remove it as the default and stick to the older one? 11.10 kernel share|improve this question edited Feb 26 '12 Try switching hda with sda (and hdb with sdb, and ...).

By default, the directive is left empty, which means that Kdump parses the standard kernel command line. Last edited by Starchild; 12-25-2004 at 09:29 AM. Solution is here: https://bugzilla.redhat.com/bugzilla....cgi?id=126953 Quote: Additional Comment #1 From C.Laurence Gonsalves on 2004-06-30 14:50 ------- It looks like the problem was due to the initrd being incomplete. Vfs Cannot Open Root Device Redhat Password Fedora This forum is for the discussion of the Fedora Project.

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 Please Append A Correct Root= Boot Option Then one day I compiled a new kernel and got the UDF-fs: No partition found error. I had a faulty CD-Rom, removing that everything worked fine! –lucacerone Mar 13 '12 at 17:36 add a comment| up vote 0 down vote After reading this answer which explains what find more Welcome, Guest.

By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Please Append A Correct Root= Boot Option Here Are The Available Partitions Why is this C++ code faster than my hand-written assembly for testing the Collatz conjecture? And I see haven't added sdc yet either. This is your problem 1: Check whether the parsed Kdump command line is clean of all kinds of weird items that might conflict with the loading of the kernel.

Please Append A Correct Root= Boot Option

Join Us! 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.. Vfs Cannot Open Root Device Or Unknown-block(0 0) This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option If it is another digit (like 8), it is unable to identify the file system (but is able to access the hardware).

Pay special attention to items like mem, memmap and others, which hardcode memory allocations. http://sauvblog.com/cannot-open/cannot-open-root-device-label-or-unknown-block0-0.html 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 You will notice I am not giving you any specific instructions, because every system is different. Vfs Cannot Open Root Device Centos

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 Normally, Kdump gets its information from two sources. Distribution: Fedora 7 Posts: 65 Original Poster Rep: Thanx, but I actually tried that, out of desperation and tiredness. have a peek here The partitions were also resized to take advantage of the increased disc-space.

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). Vfs Cannot Open Root Device Label Or 00 00 Hot Network Questions Teenage daughter refusing to go to school What was Stan Lee's character reading on the bus in Doctor Strange If I receive written permission to use content from 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:

Browse other questions tagged 11.10 kernel or ask your own question.

I may have seen this problem with reiser3 also....not sure. Normally, basic drivers for hardware initialization are included in the initrd image. I am tring to compile a new kernel from 2.6.10-1.771_FC2 to shrink the size of the modules and image. Cannot Open Root Device Mapper/volgroup-lv_root You most likely don't, so here's a quick check-up.

So what gives? addFieldToFilter() And Condition in magento2 What is the total sum of the cardinalities of all subsets of a set? And also the one mentioned in the error msg. Check This Out What is with the speech audience?

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. I notice that after the computer probes for IDE interfaces it brings up hda and it doesn't know what fs it is. That's the portable disc, btw. 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

It can be sdb4, sdc6 or something else. asked 5 years ago viewed 35874 times active 3 years ago Linked 3 Kernel panic in version 3.0.0-13 prevents login (“VFS not syncing” error) Related 1Kernel panic: unable to mount root So there appears to be a problem in the way the FC2 installer constructs the initrd that it installs on some systems. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed

Registration is quick, simple and absolutely free. Under /proc/iomem, you will see the memory reservations, which define blocks of kernel memory that can or cannot be allocated. Avi for his ideas and help with this thingie! Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us.

Ask Ubuntu works best with JavaScript enabled [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index] VFS: Cannot open root device "LABEL=/" or 00:00 From: "Evan 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 The problem will usually manifest after kernel upgrades. Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 12-23-2004, 12:29 AM #4 masand LQ Guru Registered: May 2003 Location:

Not the answer you're looking for? 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 How can you know if memory allocations are ok? It was originally created with PQ:s Partition Magic 8.0, but that program can't resize it either.