LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 12-22-2004, 12:49 PM   #1
Starchild
Member
 
Registered: Sep 2003
Location: At a tea party with Alice in Wonderland.
Distribution: Fedora 7
Posts: 65

Rep: Reputation: 15
Arrow FC2; VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)


I haven't managed to find a solution to this. I've seen different people getting this or a similar error, but for different reasons.
I've put the background info a bit further down.


Description of the error:
Full error Message:
VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel Panic - not syncing: VFS Unable to mount root fs on unknown-block(0,0)

After this, the system hangs.

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 filesystem)

The kernels I've tried are all stock kernels;
2.6.9-1.6_FC2
2.6.9-1.3_FC2
2.6.7-1.494
2.6.5-1.358
Same result with all of them.

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.  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 Core (2.6.9-1.6_FC2)
	root (hd1,4)
	kernel /vmlinuz-2.6.9-1.6_FC2 ro root=LABEL=/
	acpi=ht
	initrd /initrd-2.6.9-1.6_FC2.img
title Fedora Core (2.6.9-1.3_FC2)
	root (hd1,4)
	kernel /vmlinuz-2.6.9-1.3_FC2 ro root=LABEL=/
	acpi=ht
	initrd /initrd-2.6.9-1.3_FC2.img
title Fedora Core (2.6.8-1.521)
	root (hd1,4)
	kernel /vmlinuz-2.6.8-1.521 ro root=LABEL=/
	initrd /initrd-2.6.8-1.521.img
title Fedora Core (2.6.7-1.494.2.2)
	root (hd1,4)
	kernel /vmlinuz-2.6.7-1.494.2.2 ro root=LABEL=/
	initrd /initrd-2.6.7-1.494.2.2.img
title Fedora Core (2.6.6-1.435.2.3)
	root (hd1,4)
	kernel /vmlinuz-2.6.6-1.435.2.3 ro root=LABEL=/
	initrd /initrd-2.6.6-1.435.2.3.img
title Fedora Core (2.6.5-1.358)
	root (hd1,4)
	kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/
	initrd /initrd-2.6.5-1.358.img
title Windows
	rootnoverify (hd0,1)
	makeactive
	chainloader +1
The drive itself is a SATA drive; Maxtor 7Y250M0

I've tried root=/dev/sdb6 ,(my root partition) but no dice.


Background
I got a new PC.
My old PC has 1 120Gb Hd with win and 1 30 Gb hd with linux (both PATA).
My new PC has 2 250Gb SATA drives + 1 160Gb portable PATA hd.

I tansfered my old linux system with dd to the new computer via the portable drive. So fara so good. The partitions were also resized to take
advantage of the increased disc-space. Though I could not resize the root partiton for some reason.
parted says that it has some oddities, that may cause (fixable) problems. Though it has always said that, iirc. It was originally created with PQ:s Partition Magic 8.0, but that program can't resize it either.

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 a few, but none irreversible, and they were caused by my own silliness ).

fstab is also updated to reflect the new hd layout.

All is booting fine on the old computer.


Any suggestions appreciated.
I'm also considering upgrading to FC3, hoping that that might kill the problem.

Thanx in advance!

Last edited by Starchild; 12-25-2004 at 08:29 AM.
 
Old 12-22-2004, 03:22 PM   #2
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
hi there

is ur root partitoon
/dev/sdb6 or /dev/sdb5 ???

regards
 
Old 12-22-2004, 03:30 PM   #3
Starchild
Member
 
Registered: Sep 2003
Location: At a tea party with Alice in Wonderland.
Distribution: Fedora 7
Posts: 65

Original Poster
Rep: Reputation: 15
Hi

root partition is /dev/sdb6 ,ie, it's the partition directly after the boot partition.

cat /proc/partitions for anyone interested:
Code:
major minor  #blocks  name

   7     0      73420 loop0
   8     0  244198584 sda
   8     1    5186128 sda1
   8     2  239009400 sda2
   8    16  244198584 sdb
   8    17          1 sdb1
   8    18       8001 sdb2
   8    21      88326 sdb5
   8    22   29101716 sdb6
   8    23  213945606 sdb7
   8    24    1052226 sdb8
   8    32  156290904 sdc
   8    33   88357468 sdc1
   8    34   67930852 sdc2
fstab:
Code:
LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
/dev/sdb8               swap                    swap    defaults        0 0
/dev/cdrom              /mnt/cdrom              udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu 0 0
/dev/sda5		/mnt/ryoko		vfat	noauto,owner,users 0 0
/dev/sda2		/mnt/washu		ntfs	noauto,owner,users,ro,umask=0222,nls=utf8	0 0
none                    /var/lib/jack/tmp       tmpfs   defaults         0 0
/dev/cdrom1             /mnt/cdrom1             udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/sdb7		/mnt/sasami		ext3	defaults	0 0
ok, /dev/sda5 doesn't exist yet, but I can't see how that could cause the problem.
And I see haven't added sdc yet either. That's the portable disc, btw.

Last edited by Starchild; 12-22-2004 at 04:04 PM.
 
Old 12-22-2004, 11:29 PM   #4
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
thats what I am saying,
if ur root partiton is /dev/sdb6 then i think u should change this entry

root (hd1,4)
to
root (hd1,5)

regards
 
Old 12-23-2004, 03:01 AM   #5
Starchild
Member
 
Registered: Sep 2003
Location: At a tea party with Alice in Wonderland.
Distribution: Fedora 7
Posts: 65

Original Poster
Rep: Reputation: 15
Thanx, but I actually tried that, out of desperation and tiredness.
However, that root command above kernel, root (hd1,4), is used by grub to find the boot partition.
The kernel image is relative to this path. The kernel images are found and loaded fine, until we need the stuff on root.
So that is as it should be.
(Btw setting this to hd1,5 will cause the system to hang much earlier with a different error message, as I have no kernel images on hd1,5.)

The second root (root=LABEL=/), is a kernel command-line parameter. And also the one mentioned in the error msg.

Thanx anyway.
 
Old 12-25-2004, 04:36 AM   #6
Starchild
Member
 
Registered: Sep 2003
Location: At a tea party with Alice in Wonderland.
Distribution: Fedora 7
Posts: 65

Original Poster
Rep: Reputation: 15
*hopeful bump*
 
Old 12-25-2004, 06:28 AM   #7
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
hey i am out of options here
all the problms that i have seen have occered due to

incorrect entry in grub.conf
or
using kernel with no ext3/ext2 / FS support
or
sometimes when i have grub.conf on non-primary master hdd
then too some grub reacts ina undefined way, so i keep grub on primary hdd

regards
 
Old 12-25-2004, 07:26 AM   #8
Starchild
Member
 
Registered: Sep 2003
Location: At a tea party with Alice in Wonderland.
Distribution: Fedora 7
Posts: 65

Original Poster
Rep: Reputation: 15
Unhappy

Well, thanx for your help and effort.

As far as I can tell, my grub.conf i sound.
The fs support is there.
grub.conf is on a secondary master, though this hasn't been a problem in the past.

Anyhoo, I tried to uppgrade to FC 3, see if that will solve it. Guessing it has a later version of grub as well, not that I've checked.
Ran in to an unrelated install bug, though one with a workaround, so it'll take a while longer to know if uppgradeing will fix it.
 
Old 12-25-2004, 08:23 AM   #9
Starchild
Member
 
Registered: Sep 2003
Location: At a tea party with Alice in Wonderland.
Distribution: Fedora 7
Posts: 65

Original Poster
Rep: Reputation: 15
Lightbulb Fixed!

Ok solved the problem!
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. In
particular, I think it was missing the ata_piix module. 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 refer to the output of the above
command

- I changed the root= option to use /dev/sda3

My system is now able to boot again. So there appears to be a problem
in the way the FC2 installer constructs the initrd that it installs on
some systems.
Now my system boots up as it should!

Though, I still have root=LABEL=/ as kernel parameter, not root=/dev/sdb6

Now I have a few other things to fix, as my new keyboard is usb now, not ps/2...
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 solve this on my own.

Thanx again for the help and effort, btw.

Last edited by Starchild; 12-25-2004 at 02:07 PM.
 
Old 09-25-2005, 12:59 AM   #10
Ionexchange
LQ Newbie
 
Registered: Apr 2004
Location: Tampa, Fl
Distribution: Fedora Core 2 and 3
Posts: 21

Rep: Reputation: 15
I am having a simillar problem. I am tring to compile a new kernel from 2.6.10-1.771_FC2 to shrink the size of the modules and image. 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 kernel panic.

I notice that after the computer probes for IDE interfaces it brings up hda and it doesn't know what fs it is. Is there something I should have compiled that involves the root filesystem that I forgot. I thought I compiled all EXT2 and EXT3 support.
 
Old 12-24-2005, 06:52 AM   #11
InspectorClusea
LQ Newbie
 
Registered: Mar 2004
Distribution: Mandrake 10 CE
Posts: 3

Rep: Reputation: 0
Exclamation UDF-fs: No partition found : My solution! It's reiserfs.

My story is this:

I've been using the reiser file system for years and have been very happy with it and have kept up with new releases as they were available. Then one day I compiled a new kernel and got the UDF-fs: No partition found error.

I tried everything to resolve this problem and searched the web for an answer with no luck. 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. I researched and tried every suggestion to fix the problem.

Then I finally narrowed it down to the filesystem. The file system I was using was the new reiser4. I may have seen this problem with reiser3 also....not sure. It seems that when you compile a new kernel, the reiser file system will not access the hard drive without some manipulation with the reiserfs tools.

This also fixed a problem with compiling the NVidia graphics driver.

I reinstalled using the ext3 file system and now have no problem with the UDF-fs: No partition found error or the NVidia driver.

Also: I find that the ext3 file system works every bit as fast and good as the reiser file system. I guess I'll stick with ext3 from now on.
 
Old 01-18-2006, 03:39 AM   #12
assa9
LQ Newbie
 
Registered: Jan 2006
Posts: 2

Rep: Reputation: 0
root=

I have nonstandard boot configuration so I get lots of practice with booting weirdness....I have to have my jaz drive on the first channel of my 39160 because of the 50 pin connector but plugging a u160 device to this channel seems to slow it down ro 40or80Mhz. So.. the primary boot device is on the second channel and currently I'm booting on the second drive of the 2nd channel.

Now.. when GRUB is running it doesn't recognize the jaz drive as it is currently disabled as a boot device although I have booted from the jaz in the past - the point of all this being that grub's root device and linux's boot device are not the same thing. It is perfectly ok to point grub to a kernel on (hd0,0) and tell the kernel that you mean sdb for root.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 "cobd1" or unknown-block(117,1) lorenzobalan Linux - General 4 12-12-2007 06:19 PM
VFS: Cannot Open Root Device "Label=/" abefroman Red Hat 4 05-03-2005 09:03 AM
New kernel - VFS: Cannot open root device "301" or unknown block(3,1) j0y Debian 2 04-30-2005 09:14 PM
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


All times are GMT -5. The time now is 04:10 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration