Home > Cannot Open > Cannot Open Root Device Label Or 00 00

Cannot Open Root Device Label Or 00 00

Check if the kernel that is being boot by the boot loader is the correct kernel. please help me to solve this problem. Regards Scienitca (registered user #335819 - http://counter.li.org ) -- A master is nothing more than a student who knows something of which he can teach to other students. 03-18-2004 #3 nikhil 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 have a peek here

shibujohn View Public Profile Find all posts by shibujohn #2 18th March 2009, 03:57 PM notageek Offline Registered User Join Date: Jan 2008 Location: N/A Posts: 2,148 All They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Where should I append the correct root= option? it says above that i gotta change "LABEL=/" to "/dev/hda0" what does that mean? http://www.linuxquestions.org/questions/linux-kernel-70/vfs-cannot-open-root-device-label%3D%5C-or-00-00-a-441492/

Not a member yet? Home Search Login Register Linux Forums - Linux Help,Advice & support community:LinuxSolved.com » Linux in General » Linux Kernel » VFS:cannot open root device "LABEL=/" or 00:00 « previous next » Check if you have built in (and not as a module) support for the HDD controller you use. 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

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 I specify the actual device, e.g. "root=/dev/hda3." Now it seems that you don't have the proper device-driver loaded for your ethernet device. Join Date Apr 2004 Location India Posts 1 Kernal panic: VFS : Unable to mount root fs on 08:30 Hi I have installed fresh Fedora on Intel Server board 875wp1-E . it sound like this might be an initrd issue if the older kernel works fine.

But now I try whith 2.4.25 and then I get a problem when I try to boot with that kernal in my grub.conf: default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.20- Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Having a problem logging in? Is adding the ‘tbl’ prefix to table names really a problem?

Since the new kernel is more up to date, I would much rather try to get the other on working. more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science Check if you have built in (and not as a module) support for the bus / protocol that your harddisk controller uses. 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

If it is another digit (like 8), it is unable to identify the file system (but is able to access the hardware). Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. The site will show you which kernel drivers you need to select for your system. how do i do that?

This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. http://dekovsoft.com/cannot-open/cannot-open-root-device-cobd0.html To set a filesystem label run e2label /dev/hda2 / Alternatively in grub.conf set root= part to your partition containing your root filesystem instead of using a label. Join Us! Hyper Derivative definition.

Generally speaking one can say that, if the first digit is 0, then the kernel is unable to identify the hardware. Click Here to receive this Complete Guide absolutely free. You are currently viewing LQ as a guest. http://dekovsoft.com/cannot-open/cannot-open-root-device-302.html One of the most frequent cases: you selected support for your harddisk controller protocol (IDE, SATA, SCSI, ...) but forgot to select the HDD controller driver itself (like Intel PIIX).

The "older" kernel , 2.4.21-4.EL, is running just fine. 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 VFS: Cannot open root device "LABEL=/" or 00:00 The problem here is that the kernel that you are booting cannot translate the root=/dev/...

Logged gauravbajaj LST CareTaker Experienced Posts: 658 VFS:cannot open root device "LABEL=/" or 00:00 « Reply #1 on: June 15, 2005, 08:36:35 AM » ok its possible that ur boot directory

Fixing Unix is better than working with Windows. Where do I drop off a foot passenger in Calais (P&O)? This is not because kernels are inconsistent with each other, but because of the drivers used: older drivers use the hda syntax, newer sda. Also, recent kernels give an overview of the partitions they found on the device told.

I have seen people who, after building a first kernel (which doesn't boot), forget that they have to mount /boot before the overwrite the kernel with a new one. Thanks, Evan Follow-Ups: Re: VFS: Cannot open root device "LABEL=/" or 00:00 From: Stuart Sears [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index] [Date Prev][Date which partition is your root filesystem on? this contact form Is this Business or Tourism?

Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ Join Date Mar 2004 Location Sweden Posts 5 Kernal panic: VFS : Unable to mount root fs on 00:00 Hi I am new on linux and having proble. 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.. share|improve this answer answered Feb 27 '12 at 4:51 Nitin Venkatesh 12.6k84979 1 Hi, it passed a lot of time, but thanks.

Registration is quick, simple and absolutely free. My system is a Multi OS,redhat3 +SuSE8SP3 after I install the redhat,the suse can not be booted. Since the new kernel is more up to date, I would much rather try to get the other on working. Please try with the argument "root=/dev/sda2" let us know if it helps.

thanks venkatesh Last edited by venkatesh111; 05-04-2006 at 06:16 AM. thanks venkatesh venkatesh111 View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by venkatesh111 05-04-2006, 05:40 AM #2 lurker79 Member Registered: Jan Also I am sure the root partion is correct,but the KERNEL PINC was occured . You most likely don't, so here's a quick check-up.

using /dev/sda2 and compile with SCSI buslogic 04-01-2004 #6 nitin virmani View Profile View Forum Posts Private Message View Articles Just Joined! any help..... Not the answer you're looking for? weird ... –Dan Soap Nov 28 '11 at 16:19 add a comment| 2 Answers 2 active oldest votes up vote 7 down vote accepted You haven't provided much information with logs

if it is on /dev/hda2 for instance, try running e2label /dev/hda2 what does that show you? Try switching hda with sda (and hdb with sdb, and ...). Browse other questions tagged 11.10 kernel or ask your own question. Have you solved this issue? 03-02-2005 #8 the_unforgiven View Profile View Forum Posts Private Message View Articles Linux User Join Date Oct 2004 Location /dev/random Posts 404 title Red Hat Linux

e.g. http://nikhilk.homedns.org/projects/index.html $spacer_open $spacer_close 03-19-2004 #4 goranj View Profile View Forum Posts Private Message View Articles Just Joined! Please visit this page to clear all LQ-related cookies.