From: NeilBrown <neilb@suse.de>
To: "Vanhorn, Mike" <michael.vanhorn@wright.edu>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: md raid6 not working
Date: Tue, 21 Aug 2012 08:34:02 +1000 [thread overview]
Message-ID: <20120821083402.5e5b2fcf@notabene.brown> (raw)
In-Reply-To: <CC5802CB.287BB%michael.vanhorn@wright.edu>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
On Mon, 20 Aug 2012 19:06:17 +0000 "Vanhorn, Mike"
<michael.vanhorn@wright.edu> wrote:
>
> I have/had an 8-disk md raid 6, /dev/md0. At some point over the weekend,
> two of the disks suddently became marked as "spare" and the other has
> disappeared completely (at least as far as mdadm is concerned).
>
> All eight disks seem to be just fine, so I think the data is okay, and if
> I could just convince it to start the array with all 8 disks, I actually
> think everything would be fine. However, everything I've tried has come to
> nothing, and now I think I am stuck.
>
> Is there some way to just "force" is to change the two spare disks from
> "spare" to "active", and then let it go?
>
> Here's what I think are relevant details:
>
> The RAID is/was composed of /dev/sd[bcdefghi]1.
>
> /proc/mdstat says:
>
> # cat /proc/mdstat
> Personalities : [raid6]
> md0 : inactive sdc1[1] sdd1[10] sdi1[8] sdg1[5] sdf1[4] sde1[3] sdh1[2]
> 13674583552 blocks
>
> unused devices: <none>
> #
>
> So, here, sdb is the only one missing. However, if I try to start the array
>
> # mdadm --assemble /dev/md0
> mdadm: /dev/sdi1 has no superblock - assembly aborted
> #
What is the result of:
mdadm -S /dev/md0
mdadm -Avvv /dev/md0
??
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-08-20 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 19:06 md raid6 not working Vanhorn, Mike
2012-08-20 22:34 ` NeilBrown [this message]
2012-08-21 11:17 ` Vanhorn, Mike
2012-08-21 22:38 ` NeilBrown
2012-08-22 12:57 ` Vanhorn, Mike
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=20120821083402.5e5b2fcf@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=michael.vanhorn@wright.edu \
/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).