linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Barbuto <lucas@qk.com.au>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Order of RAID creation in boot process
Date: Wed, 29 Jan 2003 18:49:54 +1100	[thread overview]
Message-ID: <20030129074954.GA30915@qk.com.au> (raw)

Hi All,

I'm still struggling with mounting my root file system as a software
RAID-1.  As Norman Schmidt has suggested, the problem occurs because the
RAID is not created when the kernel is ready to mount it's root
partition.

I have checked the boot logs using 'dmesg' on a server that I have
installed a boot+root software RAID-1 on previously.  I noticed in that
configuration that all the RAID devices are created before the root
partition is mounted.  On my new server, the messages indicating the
RAID construction are after the root partition is mounted.  The
difference?  Well the new machine has a Promise PDC 20276 controller
(which I've disabled for the time being) and the drivers required for
this controller compiled into the kernel.  Messages about the ataraid
devices appear before the mounting of the root file system, but the md
software device messages come after that point.

Can anyone explain the timing of the software RAID construction?  How
can I get it to happen _before_ the root partition needs to be mounted?
I can't see any other differences between the two setups.  It must have
something to do with the code for the Promise ATA RAID controller,
right?

Thanks in advance.

Regards,

Lucas

             reply	other threads:[~2003-01-29  7:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29  7:49 Lucas Barbuto [this message]
     [not found] ` <3E37913D.8070005@ratnet.stw.uni-erlangen.de>
2003-01-30  2:25   ` Order of RAID creation in boot process Lucas Barbuto

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=20030129074954.GA30915@qk.com.au \
    --to=lucas@qk.com.au \
    --cc=linux-raid@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).