archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <>
To: Florian Huber <>
Cc: linux-kernel <>
Subject: Re: [2.6.0-test1-mm2] unable to mount root fs on unknown-block(0,0)
Date: 20 Jul 2003 16:17:55 -0700	[thread overview]
Message-ID: <1058743074.4425.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1058738091.5980.63.camel@localhost.localdomain>

On Sun, 2003-07-20 at 14:54, Jeremy Fitzhardinge wrote: 
>  Setting root=0303 (in your case) might helps things along.

root=0302 works for me, but root=/dev/hda2 and root=hda2 both fail, even
though /sys/block/hda/hda2/dev contains good values.

Hm, looks like try_path() in init/do_mounts.c generates paths which
don't exist.  If you specify root=/dev/hda2, try_paths will look in 
/sys/block/hda2/dev, but it needs to be /sys/block/hda/hda2/dev.  I
tried playing with it a bit, but then it started trying to mount from
hda4 for no obvious reason...

But this should be enough to go on with.


  reply	other threads:[~2003-07-20 23:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 10:55 [2.6.0-test1-mm2] unable to mount root fs on unknown-block(0,0) Florian Huber
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 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1058743074.4425.2.camel@localhost.localdomain \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).