LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Password
Linux - Kernel This forum is for all discussion relating to the Linux kernel.

Notices


Reply
  Search this Thread
Old 05-04-2006, 04:17 AM   #1
venkatesh111
Member
 
Registered: Mar 2006
Posts: 34

Rep: Reputation: 15
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
 
Old 05-04-2006, 04:40 AM   #2
lurker79
Member
 
Registered: Jan 2005
Location: UK
Posts: 55

Rep: Reputation: 16
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

Last edited by lurker79; 05-04-2006 at 04:41 AM.
 
Old 05-04-2006, 05:15 AM   #3
venkatesh111
Member
 
Registered: Mar 2006
Posts: 34

Original Poster
Rep: Reputation: 15
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

Last edited by venkatesh111; 05-04-2006 at 05:16 AM.
 
Old 05-04-2006, 09:47 AM   #4
sundialsvcs
LQ Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 10,671
Blog Entries: 4

Rep: Reputation: 3945Reputation: 3945Reputation: 3945Reputation: 3945Reputation: 3945Reputation: 3945Reputation: 3945Reputation: 3945Reputation: 3945Reputation: 3945Reputation: 3945
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.)
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
VFS: cannot open root device "sda3" or unknown-block (0,0) snakeo2 Linux - Newbie 10 07-05-2012 08:23 PM
FC2; VFS: Cannot open root device "LABEL=/" or unknown-block(0,0) Starchild Fedora 11 01-18-2006 03:39 AM
VFS: Cannot Open Root Device "Label=/" abefroman Red Hat 4 05-03-2005 09:03 AM
Kernel Panic:VFS: Cannot open root device "hda3" or 00:10 shivendnrab Linux - General 1 07-01-2004 03:08 AM
VFS: Cannot open root device "1601" or unknown-block(22,1) takehora Slackware 3 06-11-2004 08:34 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel

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

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration