From: Neil Brown <neilb@cse.unsw.edu.au>
To: Jason Pfingstmann <stclists@wearesimply.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 5 and Power Failure
Date: Sat, 13 Jul 2002 10:19:32 +1000 (EST) [thread overview]
Message-ID: <15663.29204.41082.959065@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Jason Pfingstmann on Friday July 12
On Friday July 12, stclists@wearesimply.com wrote:
>
> Now, the event counter for the raid 5 array lists 3 different things - 5
> drives show event counter to be 00 00 00 38, 1 drive shows 00 00 00 28 (hda),
> and 1 drive shows 00 00 00 37 (hdd).
Looks like hda has be out-of-it for quite a while... you really need
to monitor raid status somehow.
> Even if hdd is completely bad, I can't afford to lose 250 GB of
> data...
You do have backups of course.... :-)
>
> Any ideas or suggestions?
Get mdadm
http://www.cse.unsw.edu.au/~neilb/source/mdadm/
and use
mdadm --assemble --force /dev/md0 /dev/hd......
(i.e. after the name of the array, list all the component drives).
NeilBrown
prev parent reply other threads:[~2002-07-13 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 16:22 Raid 5 and Power Failure Jason Pfingstmann
2002-07-13 0:19 ` Neil Brown [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=15663.29204.41082.959065@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=linux-raid@vger.kernel.org \
--cc=stclists@wearesimply.com \
/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).