From: Lucas Barbuto <lucas@qk.com.au>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Order of RAID creation in boot process
Date: Thu, 30 Jan 2003 13:25:20 +1100 [thread overview]
Message-ID: <20030130022520.GA1931@qk.com.au> (raw)
In-Reply-To: <3E37913D.8070005@ratnet.stw.uni-erlangen.de>
Hi Norman,
Thanks for continuing to try to help me out, I was really floundering
there for a while. I've sorted things out now. I've put my system
disks back in the primary and secondary IDE slots and I'm going to use
the ataraid slots for non-OS disks.
I've got a software RAID-0 going over hda and hdc, I'm booting off it,
I've got my root partition on it and I've got a combination of ext3 for
the root and boot partitions and XFS for the rest.
I accomplished this by installing onto hda, then creating the raid
devices across hda and hdc one by one and using the failed-disk
directive and a boot disk to make the root partition a raid device. All
standard stuff.
I've removed the ataraid and pdcraid code from the kernel and compiled
it as modules, with this setup, the md devices are created before the
root file system is mounted. I still don't really understand why they
aren't created first when ataraid and pdcraid are compiled in. I guess
there is a conflict there? I can now access hde and hdg by loading the
module after the system has booted, this will work out fine for me as
those drives will now just be used to store non-OS data (backups and
stuff).
Again, thanks for your help.
Regards,
Lucas
prev parent reply other threads:[~2003-01-30 2:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 7:49 Order of RAID creation in boot process Lucas Barbuto
[not found] ` <3E37913D.8070005@ratnet.stw.uni-erlangen.de>
2003-01-30 2:25 ` Lucas Barbuto [this message]
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=20030130022520.GA1931@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).