From: Peter Lauda <plauda@rx30.com>
To: linux-raid@vger.kernel.org
Subject: raid'ing problems
Date: 21 Oct 2005 08:50:39 -0400 [thread overview]
Message-ID: <1129899043.32525.4.camel@plauda5.rx30.com> (raw)
If anyone is listening....
I have read the howto's and all the FAQ's I can find. I am trying to do
the following and having zero success:
An installed system needs to have a second disk setup with the first as
a raid 1 set.
I have been able to boot from a CD and create the md0 md1 and md2
devices. I cannot however, get any of these to mount afterwards. I
assume that mount doesn't know what type of fs these are and I'm not
seeing anything in the docs about what type I can use.
Eventually this raid set needs to be able to boot. We use grub as the
boot loader. If anyone has done this or knows how and can offer any
assistance I thank you in advance.
We are using 2.4.29 kernel in a home rolled package but have both
raidtools and mdadm tools available.
Cheers!
--p
next reply other threads:[~2005-10-21 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 12:50 Peter Lauda [this message]
2005-10-21 15:58 ` raid'ing problems Andy Dawson
2005-10-21 16:01 ` Brad Dameron
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=1129899043.32525.4.camel@plauda5.rx30.com \
--to=plauda@rx30.com \
--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