linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Florian Huber <florian.huber@mnet-online.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.0-test1-mm2] unable to mount root fs on unknown-block(0,0)
Date: 20 Jul 2003 14:54:52 -0700	[thread overview]
Message-ID: <1058738091.5980.63.camel@localhost.localdomain> (raw)
In-Reply-To: <20030720125547.11466aa4.florian.huber@mnet-online.de>

On Sun, 2003-07-20 at 03:55, Florian Huber wrote:
> 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 unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)

I'm getting the same thing, with an ext3 root.  It seems that something
odd is happening in init/do_mounts.c, since from the message it looks
like ROOT_DEV isn't being initialized.  However the mm2 patch doesn't
seem to change anything significant-looking in this directory (just some
headers).  

Hm, on closer inspection, it resolves the device name by mounting sysfs,
rummaging around to see if the device exists and gets its device number
(0301 for hda1) and initializes ROOT_DEV from that.  I wonder if there's
a sysfs/block device breakage which makes the partitions not appear in
sysfs?  Setting root=0303 (in your case) might helps things along.

	J


  parent reply	other threads:[~2003-07-20 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 10:55 Florian Huber
2003-07-20 11:55 ` Felipe Alfaro Solana
2003-07-20 18:47   ` Joe
2003-07-20 21:54 ` Jeremy Fitzhardinge [this message]
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=1058738091.5980.63.camel@localhost.localdomain \
    --to=jeremy@goop.org \
    --cc=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).