Re: Kernelpanic - not syncing: VFS: Unable to mount root fs onunknown-block
From: Chris Gorman
Date: Fri Apr 29 2005 - 20:26:37 EST
First off, I am not on the linux-kernel list so please cc me directly on
this if anyone has a solution. I've experienced a very similar problem
as S S did while upgrading from 126.96.36.199 to 188.8.131.52. Essentialy grub
will boot 184.108.40.206 without any problems, but using the same command line
220.127.116.11 fails to boot with "Cannot open root device hde6 or
unknown-block(0,0)". The config file used was the same one as 18.104.22.168 so
I doubt I missed a config option.
The reason I chose to upgrade was because I've been getting ext3 errors
which caused the journal to crash and the filesystem to be remounted
read-only. I hoped the following referenced patch would resolve it.
[PATCH] Prevent race condition in jbd
From: Stephen Tweedie <sct@xxxxxxxxxx>
Subject: Prevent race condition in jbd
This patch from Stephen Tweedie which fixes a race in jbd code (it
demonstrated itself as more or less random NULL dereferences in
the journal code).
Acked-by: Jan Kara <jack@xxxxxxx>
Acked-by: Chris Mason <mason@xxxxxxxx>
Signed-off-by: Chris Wright <chrisw@xxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>
I only see a few other patches in the Changelog and none appear to me to
be fs relevant. Could this be part of our problem? I've seen one other
post "Re: Linux 2.6.12-rc2" by hubert.tonneau@xxxxxxxxxxxxxx which
describes the same symptom. The problem occured during an upgrade from
2.6.11 to 2.6.12-rc and this person does have ext3 compiled in.
Also, since grub is common between myself and S S, and my grub is a little
old, I will try upgrading the program in case that is the problem.
On Apr 18, 2005 S S wrote:
> I compiled linux kernel 22.214.171.124 on RHEL and while
> rebooting I get this
> error message -
> Cannot open root device /SCSIGroup00/SCSIVol000
> Please append a correct "root=" boot option
> Kernelpanic - not syncing: VFS: Unable to mount root
> fs on
> unknown-block 0,0
> This root entry in grub .conf is identical to kernel
> image entry 2.6.9 which boots fine. However 126.96.36.199
> compiled kernel does not find
> Could anyone please suggest what could be going wrong.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/