From: "janaka@clanwind.com" <janaka@clanwind.com>
To: linux-raid@vger.kernel.org
Subject: Failed RAID5
Date: Thu, 12 May 2005 02:43:23 -0600 [thread overview]
Message-ID: <4283172b.242.630.20549@clanwind.com> (raw)
Hey,
I am trying to rebuild a failed raid 5. I have one disk
that's bad, and one disk that, in the confusion, has become
convinced that it is a spare. I don't know where it got
this idea, but I have drive "mdadm --assemble --force
/dev/md2 /dev/hda3 /dev/hdc3 /dev/hde3 /dev/hdg3 /dev/hdi3
/dev/hdk3" as well as "mkraid --force /dev/md2" and my
raidtab hasn't changed except to state that HDA has failed.
Is there anyway for me to force the "spare disk" to
reconsider its purpose in life? Which is presently to make
my data accessable so I can move to raid 10 or some other
more simple raid format.
I mean, I am sure it is some bit in the superblock that is
miss set, but how do I fix that?
Thanks
-fro
next reply other threads:[~2005-05-12 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 8:43 janaka [this message]
2005-05-12 10:05 ` Failed RAID5 Neil Brown
2005-05-12 14:52 ` Mike Tran
-- strict thread matches above, loose matches on Subject: below --
2013-10-20 18:30 failed raid5 i.mikic
2013-10-21 8:24 ` Mikael Abrahamsson
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=4283172b.242.630.20549@clanwind.com \
--to=janaka@clanwind.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;
as well as URLs for NNTP newsgroup(s).