linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Herbert Pötzl" <herbert@13thfloor.at>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test3 cannot mount root fs
Date: Tue, 12 Aug 2003 16:06:09 +0200	[thread overview]
Message-ID: <20030812140609.GB1926@www.13thfloor.at> (raw)
In-Reply-To: <E19mZ6L-000Jrv-00.arvidjaar-mail-ru@f22.mail.ru>

On Tue, Aug 12, 2003 at 05:22:13PM +0400, "Andrey Borzenkov"  wrote:
> 
> >>        cannot mount rootfs "NULL" or hdb1
> >
> > AFAIK, there is no such message in 2.6.0-test3 ...
> 
> there is

please provide the file and line number, where
linux-2.6.0-test3 contains the string "cannot mount rootfs".
(or where this string is synthesized)
I am not able to locate it ...

> > if, on the other hand, the message looks like ...
> >
> > -----------
> > VFS: Cannot open root device "hdb1" or unknown-block(0,0)
> > Please append a correct "root=" boot option
> > -----------
> 
> he does not pass it in append line. He is using root= option in lilo.
> actually my lilo does pass "root=341" in this case while the above means lilo omits any root= command line option and relies on compiled-in ROOT_DEV

already suggested that, but he says, it doesn't
work either ... 

best,
Herbert

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2003-08-12 14:05 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 13:22 2.6.0-test3 cannot mount root fs "Andrey Borzenkov" 
2003-08-12 14:06 ` Herbert Pötzl [this message]
2003-08-12 14:21   ` Christophe Saout
  -- strict thread matches above, loose matches on Subject: below --
2003-08-12 14:16 "Andrey Borzenkov" 
2003-08-12 13:23 "Andrey Borzenkov" 
2003-08-12 20:43 ` Norbert Preining
2003-08-13  5:17   ` "Andrey Borzenkov" 
2003-08-12  7:37 Daniel Blueman
2003-08-09 10:46 gaxt
2003-08-09 10:40 ` Norbert Preining
2003-08-09 11:56   ` Herbert Pötzl
2003-08-09  9:07     ` Norbert Preining
     [not found]       ` <20030809130641.A8174@electric-eye.fr.zoreil.com>
     [not found]         ` <01a201c35e65$0536ef60$ee52a450@theoden>
2003-08-09 11:58   ` Henrik Storner
2003-08-09 13:48   ` Felipe Alfaro Solana
2003-08-09 14:32 ` Mr. James W. Laferriere
2003-08-09 14:48   ` gaxt
2003-08-09 14:38     ` Mr. James W. Laferriere
2003-08-09 15:01     ` Henrik Ræder Clausen
2003-08-10 21:17   ` Norbert Preining
2003-08-10 22:43     ` Andrew Morton
2003-08-11  5:34       ` Norbert Preining
2003-08-11 14:59         ` Herbert Pötzl
2003-08-11 15:40           ` Norbert Preining
2003-08-11 18:53             ` Herbert Pötzl
2003-08-11 21:50               ` Norbert Preining
2003-08-11 22:21                 ` Herbert Pötzl
2003-08-12  1:52                   ` Mark W. Alexander
2003-08-12  6:28                     ` Norbert Preining
2003-08-12  5:39                   ` Norbert Preining
2003-08-12 12:26                     ` Herbert Pötzl
2003-08-12 12:31                       ` Norbert Preining
2003-08-12 12:44                       ` jeff millar
2003-08-12 23:52                         ` Thomas Molina
2003-08-13 16:59                           ` Paul Dickson
2003-08-14  4:09                             ` jeff millar

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=20030812140609.GB1926@www.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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
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).