From: NeilBrown <neilb@suse.de>
To: Ian Young <ian@duffrecords.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: not enough operational mirrors
Date: Mon, 22 Sep 2014 15:47:17 +1000 [thread overview]
Message-ID: <20140922154717.6cd3cab2@notabene.brown> (raw)
In-Reply-To: <CANs+QMzWWqh-5MemOrbguaq7fNzJPDaYUH66K0rgGrnaXY7FNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
On Sun, 21 Sep 2014 22:32:19 -0700 Ian Young <ian@duffrecords.com> wrote:
> My 6-drive software RAID 10 array failed. The individual drives
> failed one at a time over the past few months but it's been an
> extremely busy summer and I didn't have the free time to RMA the
> drives and rebuild the array. Now I'm wishing I had acted sooner
> because three of the drives are marked as removed and the array
> doesn't have enough mirrors to start. I followed the recovery
> instructions at raid.wiki.kernel.org and, before making things any
> worse, saved the status using mdadm --examine and consulted this
> mailing list. Here's the status:
>
> http://pastebin.com/KkV8e8Gq
>
> I can see that the event counts on sdd2 and sdf2 are significantly far
> behind, so we can consider that data too old. sdc2 is only behind by
> two events, so any data loss there should be minimal. If I can make
> the array start with sd[abce]2 I think that will be enough to mount
> the filesystem, back up my data, and start replacing drives. How do I
> do that?
Use the "--force" option with "--assemble".
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-09-22 5:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 5:32 not enough operational mirrors Ian Young
2014-09-22 5:47 ` NeilBrown [this message]
2014-09-22 17:17 ` Ian Young
2014-09-22 23:53 ` NeilBrown
2014-09-23 0:55 ` Ian Young
2014-09-23 17:07 ` Ian Young
2014-10-05 21:43 ` Ian Young
[not found] ` <CANs+QMwUWZ+z0Kk-voHRLZaherOh8K8o_gCXVvw7nnXYT_goUg@mail.gmail.com>
2014-09-22 23:09 ` Ian Young
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=20140922154717.6cd3cab2@notabene.brown \
--to=neilb@suse.de \
--cc=ian@duffrecords.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).