From: Scott Sinno <sinno@sinno.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid@vger.kernel.org, "Vaughan,
Garrison (GSFC-606.2)[INTERNATIONAL TECHNOLOGY COALITION,
INC]" <garrison.r.vaughan@nasa.gov>
Subject: Re: RAID6 won't reassemble after disk controller failure
Date: Wed, 25 Mar 2015 11:26:34 -0400 [thread overview]
Message-ID: <5512D3AA.5000003@sinno.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1503251621390.20507@uplift.swm.pp.se>
Mikael Abrahamsson wrote:
> I would recommend you to not do that unless there is no other way out.
Wholeheartedly agreed, thus looking to this list for guidance first :-)
>
> Please post dmesg output from the --assemble --force attempt, it might
> contain reason why the assembly was unsuccessful.
>
It doesn't appear to be very telling. Note that per the provided
'-E'(examine) output, event count is off a bit on some of the drives,
and several report 'missing'
#dmesg output
md: bind<sdbk>
md: bind<sdbl>
md: bind<sdbm>
md: bind<sdbn>
md: bind<sdbo>
md: bind<sdbp>
md: bind<sdbq>
md: bind<sdbi>
md: bind<sdbr>
md: bind<sdbs>
md: bind<sdbt>
md: bind<sdbj>
md: md10 stopped.
md: unbind<sdbj>
md: export_rdev(sdbj)
md: unbind<sdbt>
md: export_rdev(sdbt)
md: unbind<sdbs>
md: export_rdev(sdbs)
md: unbind<sdbr>
md: export_rdev(sdbr)
md: unbind<sdbi>
md: export_rdev(sdbi)
md: unbind<sdbq>
md: export_rdev(sdbq)
md: unbind<sdbp>
md: export_rdev(sdbp)
md: unbind<sdbo>
md: export_rdev(sdbo)
md: unbind<sdbn>
md: export_rdev(sdbn)
md: unbind<sdbm>
md: export_rdev(sdbm)
md: unbind<sdbl>
md: export_rdev(sdbl)
md: unbind<sdbk>
md: export_rdev(sdbk)
md: md10 stopped.
md: bind<sdbk>
md: bind<sdbl>
md: bind<sdbm>
md: bind<sdbn>
md: bind<sdbo>
md: bind<sdbp>
md: bind<sdbq>
md: bind<sdbi>
md: bind<sdbr>
md: bind<sdbs>
md: bind<sdbt>
md: bind<sdbj>
md: md10 stopped.
md: unbind<sdbj>
md: export_rdev(sdbj)
md: unbind<sdbt>
md: export_rdev(sdbt)
md: unbind<sdbs>
md: export_rdev(sdbs)
md: unbind<sdbr>
md: export_rdev(sdbr)
md: unbind<sdbi>
md: export_rdev(sdbi)
md: unbind<sdbq>
md: export_rdev(sdbq)
md: unbind<sdbp>
md: export_rdev(sdbp)
md: unbind<sdbo>
md: export_rdev(sdbo)
md: unbind<sdbn>
md: export_rdev(sdbn)
md: unbind<sdbm>
md: export_rdev(sdbm)
md: unbind<sdbl>
md: export_rdev(sdbl)
md: unbind<sdbk>
md: export_rdev(sdbk)
next prev parent reply other threads:[~2015-03-25 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 15:19 RAID6 won't reassemble after disk controller failure Scott Sinno
2015-03-25 15:22 ` Mikael Abrahamsson
2015-03-25 15:26 ` Scott Sinno [this message]
2015-03-25 15:29 ` Scott Sinno
2015-03-25 15:30 ` Mikael Abrahamsson
2015-03-25 15:43 ` Scott Sinno
2015-03-25 16:09 ` Mikael Abrahamsson
2015-03-25 16:16 ` Scott Sinno
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=5512D3AA.5000003@sinno.net \
--to=sinno@sinno.net \
--cc=garrison.r.vaughan@nasa.gov \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.