From: Ninti Systems <office@ninti.com.au>
To: RAID Linux <linux-raid@vger.kernel.org>
Subject: fd filesystem and RAID1
Date: 03 Apr 2004 09:02:37 +0930 [thread overview]
Message-ID: <1080948756.999.10.camel@localhost> (raw)
I've been able to do everything involved in setting up a simple RAID1
with 2 IDE disks on Slackware 9.1 except get it to actually keep working
on reboot.
I installed on one disk, built 'degraded' RAID1 devices on the second
disk, copied data, etc. I can hot add devices from the original disk to
the RAID arrays. RAID devices in /etc/fstab come up (in degraded mode)
on boot.
The problem is that hot-added devices never stick, the RAID arrays are
always degraded again on reboot.
mdadm complains of missing superblocks. I have read the man page but
can't see how to manage superblocks (create/delete) if this is even
possible.
I'm wondering if have to make the original install partitions type 'fd'
as well as those on the second disk?
next reply other threads:[~2004-04-02 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 23:32 Ninti Systems [this message]
2004-04-05 0:58 ` fd filesystem and RAID1 Daniel Pittman
2004-04-05 8:00 ` Ninti Systems
2004-04-05 9:08 ` Ninti Systems
2004-04-05 14:48 ` Daniel Pittman
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=1080948756.999.10.camel@localhost \
--to=office@ninti.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).