From: NeilBrown <neilb@suse.de>
To: Christian <cjs703@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 array won't start
Date: Sat, 12 Feb 2011 08:32:24 +1100 [thread overview]
Message-ID: <20110212083224.6b1c2cee@notabene.brown> (raw)
In-Reply-To: <AANLkTikmCmutS_96PNYR0RKAv07cG5Vje0kyzzQ7U9rd@mail.gmail.com>
On Fri, 11 Feb 2011 16:13:53 -0500 Christian <cjs703@gmail.com> wrote:
> On Fri, Feb 11, 2011 at 3:49 PM, NeilBrown <neilb@suse.de> wrote:
> > On Fri, 11 Feb 2011 11:48:41 -0500 Christian <cjs703@gmail.com> wrote:
> >
> >> Hello,
> >>
> >> I have a 10 disk RAID6 array. I had an issue with a molex connector
> >> that caused drives to drop from a 5in3 SATA backplane. There wasn't
> >> any activity occurring on the array during the time, so I think the
> >> filesystem should be in tact. The issue now is the event counts are
> >> out of sync, along with the state of each drive.
> >>
> >> # mdadm -A /dev/md1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdk1 /dev/sdl1
> >> /dev/sdm1 /dev/sdq1 /dev/sdr1 /dev/sds1 /dev/sdt1
> >> mdadm: /dev/md1 assembled from 8 drives - not enough to start the
> >> array while not clean - consider --force.
> >>
> >> # cat /proc/mdstat
> >> Personalities : [raid6] [raid5] [raid4]
> >> md1 : inactive sdt1[1](S) sde1[9](S) sdl1[8](S) sdg1[7](S) sdf1[6](S)
> >> sdk1[5](S) sdq1[4](S) sds1[3](S) sdr1[2](S) sdm1[0](S)
> >> 19535134720 blocks
> >>
> >>
> >> # mdadm -Af /dev/md1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdk1 /dev/sdl1
> >> /dev/sdm1 /dev/sdq1 /dev/sdr1 /dev/sds1 /dev/sdt1
> >> mdadm: failed to RUN_ARRAY /dev/md1: Input/output error
> >
> > The array is already in a partially-assembled state.
> >
> > mdadm -S /dev/md1
> >
> > before trying to assemble again with -f.
> >
> > NeilBrown
>
> I should have probably included it but I did stop the array with -S
> before running -Af.
True.
Ok, being sure that the array is stopped first, try the "-Af" command again,
but an a -v.
Then post the results together with any kernel messages (dmesg | tail -50
maybe)
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-11 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimLfJHc2waPkvjUXn=mewc37qkCd-r0GG4k=e-D@mail.gmail.com>
2011-02-11 16:48 ` RAID6 array won't start Christian
2011-02-11 20:49 ` NeilBrown
2011-02-11 21:13 ` Christian
2011-02-11 21:32 ` NeilBrown [this message]
2011-02-11 21:51 ` Christian
2011-02-11 22:36 ` Christian
2011-02-11 23:37 ` Christian
2011-02-12 0:52 ` NeilBrown
2011-02-12 0:57 ` Christian
2011-02-12 1:03 ` NeilBrown
2011-02-12 4:08 ` Christian
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=20110212083224.6b1c2cee@notabene.brown \
--to=neilb@suse.de \
--cc=cjs703@gmail.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