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 11:52:35 +1100 [thread overview]
Message-ID: <20110212115235.5e38c3db@notabene.brown> (raw)
In-Reply-To: <AANLkTi=em0Wkj48SOECZqSuyJ01AwDnDdE76aQPzWiTp@mail.gmail.com>
On Fri, 11 Feb 2011 17:36:08 -0500 Christian <cjs703@gmail.com> wrote:
> Here it is again, there were a few other messages in there at the beginning.
>
> [70745.855861] md: md1 stopped.
> [70745.859303] md: bind<sdm1>
> [70745.859576] md: bind<sdr1>
> [70745.859720] md: bind<sds1>
> [70745.860265] md: bind<sdq1>
> [70745.860428] md: bind<sdk1>
> [70745.860680] md: bind<sdf1>
> [70745.860839] md: bind<sdg1>
> [70745.860986] md: bind<sdl1>
> [70745.861169] md: bind<sde1>
> [70745.861359] md: bind<sdt1>
> [70745.861407] md: kicking non-fresh sds1 from array!
> [70745.861411] md: unbind<sds1>
> [70745.870570] md: export_rdev(sds1)
> [70745.870598] md: kicking non-fresh sdm1 from array!
That shouldn't happen when you use -f ....
Could be that you hit the mdadm bug fixed by commit 67a8c82d606
which is in mdadm-2.6
What version of mdadm are you running???
(I note you have got your data back by other means - good!)
NeilBrown
> [70745.870602] md: unbind<sdm1>
> [70745.882561] md: export_rdev(sdm1)
> [70745.883324] md/raid:md1: not clean -- starting background reconstruction
> [70745.883333] md/raid:md1: device sdt1 operational as raid disk 1
> [70745.883335] md/raid:md1: device sde1 operational as raid disk 9
> [70745.883337] md/raid:md1: device sdl1 operational as raid disk 8
> [70745.883339] md/raid:md1: device sdg1 operational as raid disk 7
> [70745.883340] md/raid:md1: device sdf1 operational as raid disk 6
> [70745.883342] md/raid:md1: device sdk1 operational as raid disk 5
> [70745.883344] md/raid:md1: device sdq1 operational as raid disk 4
> [70745.883345] md/raid:md1: device sdr1 operational as raid disk 2
> [70745.884038] md/raid:md1: allocated 10572kB
> [70745.884057] md/raid:md1: cannot start dirty degraded array.
> [70745.884065] RAID conf printout:
> [70745.884066] --- level:6 rd:10 wd:8
> [70745.884068] disk 1, o:1, dev:sdt1
> [70745.884069] disk 2, o:1, dev:sdr1
> [70745.884070] disk 4, o:1, dev:sdq1
> [70745.884072] disk 5, o:1, dev:sdk1
> [70745.884073] disk 6, o:1, dev:sdf1
> [70745.884074] disk 7, o:1, dev:sdg1
> [70745.884076] disk 8, o:1, dev:sdl1
> [70745.884077] disk 9, o:1, dev:sde1
> [70745.884370] md/raid:md1: failed to run raid set.
> [70745.884372] md: pers->run() failed ...
next prev parent reply other threads:[~2011-02-12 0:52 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
2011-02-11 21:51 ` Christian
2011-02-11 22:36 ` Christian
2011-02-11 23:37 ` Christian
2011-02-12 0:52 ` NeilBrown [this message]
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=20110212115235.5e38c3db@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