From: Florian Huber <florian.huber@mnet-online.de>
To: linux-kernel@vger.kernel.org
Subject: [2.6.0-test1-mm2] unable to mount root fs on unknown-block(0,0)
Date: Sun, 20 Jul 2003 12:55:47 +0200 [thread overview]
Message-ID: <20030720125547.11466aa4.florian.huber@mnet-online.de> (raw)
Hello ML,
I can't boot my 2.6.0-test1-mm2 kernel (+GCC 3.3). The kernel panics
at bootime:
VFS: Cannot open root device "hda3" or unknow-block(0,0)
Please append a correct "root=" boot option
Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
I do have compiled support for the file system on my root partition
(xfs). The same configuration worked well with 2.6.0-test1-mm1.
Perhaps somebody knows how to solve this.
TIA
Florian Huber
next reply other threads:[~2003-07-20 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 10:55 Florian Huber [this message]
2003-07-20 11:55 ` Felipe Alfaro Solana
2003-07-20 18:47 ` Joe
2003-07-20 21:54 ` Jeremy Fitzhardinge
2003-07-20 23:17 ` Jeremy Fitzhardinge
2003-07-21 15:38 ` Florian Huber
2003-07-21 18:05 ` Christian Axelsson
2003-07-23 18:42 ` [PATCH 2.6.0-test1-mm2] fix unable to mount root fs Daniel McNeil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030720125547.11466aa4.florian.huber@mnet-online.de \
--to=florian.huber@mnet-online.de \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [2.6.0-test1-mm2] unable to mount root fs on unknown-block(0,0)' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).