From: Jean Jordaan <jean@upfrontsystems.co.za>
To: linux-raid@vger.kernel.org
Subject: Recovering RAID5 array
Date: Tue, 20 Jan 2004 08:54:55 +0200 [thread overview]
Message-ID: <400CD0BF.2010808@upfrontsystems.co.za> (raw)
Hi all
I'm having a RAID week. It looks like 1 disk out of a
3-disk RAID5 array has failed. The array consists of
/dev/hda3 /dev/hdb3 /dev/hdc3 (all 40Gb)
I'm not sure which one is physically faulty. In an attempt
to find out, I did:
mdadm --manage --set-faulty /dev/md0 /dev/hda3
The consequence of this was 2 disks marked faulty and no
way to get the array up again in order to use raidhotadd
to put that device back.
I'm scared of recreating superblocks and losing all my data.
So now I'm doing 'dd if=/dev/hdb3 of=/dev/hdc2' of all three
RAID partitions so that I can work on a *copy* of the data.
Then I aim to
mdadm --create /dev/md0 --raid-devices=3 --level=5 \
--spare-devices=1 --chunk=64 --size=37111 \
/dev/hda1 /dev/hda2 missing /dev/hdb1 /dev/hdb2
hda2 is a copy of the partition of the drive I'm currently
suspecting of failure. hdb2 is a blank partition.
I've been running Seagate's drive diagnostic software
overnight, and the old disks check out clean. This makes me
afraid that it's reiserfs corruption, not a RAID disk
failure :/
Does anyone here have any comments on what I've done so far,
or if there's anything better I can do next?
--
Jean Jordaan
http://www.upfrontsystems.co.za
next reply other threads:[~2004-01-20 6:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 6:54 Jean Jordaan [this message]
2004-01-20 6:59 ` Recovering RAID5 array Neil Brown
2004-01-20 7:17 ` Jean Jordaan
2004-01-20 8:08 ` Jean Jordaan
2004-01-20 9:59 ` Neil Brown
2004-01-20 10:40 ` Jean Jordaan
2004-01-20 12:10 ` Maarten v d Berg
2004-01-20 12:23 ` Jean Jordaan
2004-01-20 12:57 ` Maarten v d Berg
2004-01-20 13:28 ` Jean Jordaan
2004-01-20 10:44 ` Jean Jordaan
2004-01-20 7:22 ` Guy
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=400CD0BF.2010808@upfrontsystems.co.za \
--to=jean@upfrontsystems.co.za \
--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).