LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   VFS: cannot open root device "LABEL=\" or 00:00 (https://www.linuxquestions.org/questions/linux-kernel-70/vfs-cannot-open-root-device-label%3D%5C-or-00-00-a-441492/)

venkatesh111 05-04-2006 04:17 AM

VFS: cannot open root device "LABEL=\" or 00:00
 
hi i have recompiled my kernel with few modification i have comliped the kernel using fallowing commands

make clean
make mrproper
make xconfig
make dep
make
make modules
make modules_install
make bzImage
make install

then i rebooted system with my new kernel but there was error saying:

VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" option


my grub.conf is as fallows:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,3)
# kernel /boot/vmlinuz-version ro root=/dev/hda4
# initrd /boot/initrd-version.img
#boot=/dev/hda
default=2
timeout=500500500500500
splashimage=(hd0,3)/boot/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2115.nptlcustom)
root (hd0,3)
kernel /boot/vmlinuz-2.4.22-1.2115.nptlcustom ro root=LABEL=/ rhgb
initrd /boot/initrd-2.4.22-1.2115.nptlcustom.img
title Fedora Core (2.4.22-1.2115.nptl)
root (hd0,3)
kernel /boot/vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/ rhgb
initrd /boot/initrd-2.4.22-1.2115.nptl.img
title windows
rootnoverify (hd0,0)
chainloader +1


any idea wt should i do.........

thanks
venkatesh

lurker79 05-04-2006 04:40 AM

The error is because the kernel is looking for your root filsystem by using a filesystem label, it is looking for the filesystem labelled / and is unable to find it. Either your root filesystem is not labelled correctly or not labelled at all.

which partition is your root filesystem on?
if it is on /dev/hda2 for instance, try running
e2label /dev/hda2
what does that show you? if it returns nothing it means that there isn;t a filesystem label associated with that parition.
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.
e.g.
kernel /boot/vmlinuz-2.4.22-1.2115.nptlcustom ro root=/dev/hda2 rhgb

venkatesh111 05-04-2006 05:15 AM

thanks it worked my root file system was on hda4 so i changed the line

kernel /boot/vmlinuz-2.4.22-1.2115.nptlcustom ro root=LABEL=/ rhgb

to

kernel /boot/vmlinuz-2.4.22-1.2115.nptlcustom ro root=/dev/hda4 rhgb

and it worked

but i cannot access internet in my new kernel

i checked my eth0 connection it is inactive i tried to activate it but i recive an error msg saying:

interface 'eth0' not found
8139too device eth0 does not seem to be
present, delaying initialization.

any help.....

thanks

venkatesh

sundialsvcs 05-04-2006 09:47 AM

I've never been able to get 'root=LABEL=' to work. 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. The easiest way to find out which one is needed is to boot up a LiveCD, then do lsmod to see which driver module was loaded.

I prefer to put all of the device-drivers required by my hardware directly into the kernel... omitting the many-dozens of others that are typically included with a "distro." (If and when the hardware changes, presumably I'll know that I did it and will have prepared ahead of time.)


All times are GMT -5. The time now is 07:13 PM.