From: Ookhoi <ookhoi@ookhoi.xs4all.nl>
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.12 cannot find root device on raid
Date: Thu, 25 Oct 2001 21:57:44 +0200 [thread overview]
Message-ID: <20011025215743.B24475@humilis> (raw)
In-Reply-To: <15319.38517.663820.504760@notabene.cse.unsw.edu.au> <htYB7.5102$d%.933992639@newssvr17.news.prodigy.com>
In-Reply-To: <htYB7.5102$d%.933992639@newssvr17.news.prodigy.com>
> In article <15319.38517.663820.504760@notabene.cse.unsw.edu.au>,
> Neil Brown <neilb@cse.unsw.edu.au> wrote:
> | On Tuesday October 23, davidsen@prodigy.com wrote:
> | >
> | > The line you provide doesn't look anything like the two forms in the
> | > md.txt you mention. Or rather it looks like a blending, but neither of
> | > them is md0= in form. I have to look at the code to see which is
> | > correct, possibly yours, since the
> | > append = "md=0,/dev/sda1,/dev/sdb1"
> | > line doesn't seem to work :-(
> |
> | Odd ... I use lines just like that. e.g.:
> | append="md=0,/dev/hda1,/dev/hde1,/dev/hdg1"
> |
> | and it works just fine. What do you get in the way of error messages?
>
> None - the system simply exits the BIOS, reads the first drive once and
> cold boots. The drive is okay, I can read both copies of the mirror end
> to end without error after booting from floppy. Lilo claims it writes to
> the md0 device, but boot fails.
I always let lilo write to the first and the second disk itself, and I
do not use any kernel parameters for sw raid. Is writing to the disks
instead of writing to /dev/md0 the wrong way? It works for me.
Ookhoi
next prev parent reply other threads:[~2001-10-25 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 13:01 2.4.12 cannot find root device on raid Norbert Preining
2001-10-18 14:56 ` Jeffrey W. Baker
2001-10-23 15:12 ` Bill Davidsen
2001-10-25 4:35 ` Neil Brown
2001-10-25 18:02 ` bill davidsen
2001-10-25 19:57 ` Ookhoi [this message]
2001-10-31 17:19 ` Bill Davidsen
2001-10-19 18:44 ` Francois Romieu
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=20011025215743.B24475@humilis \
--to=ookhoi@ookhoi.xs4all.nl \
--cc=davidsen@tmr.com \
--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