From: Phil Turmel <philip@turmel.org>
To: Digimer <lists@alteeve.ca>, linux-raid@vger.kernel.org
Subject: Re: Broken array, trying to assemble enough to copy data off
Date: Thu, 10 Oct 2013 08:44:59 -0400 [thread overview]
Message-ID: <5256A14B.7030008@turmel.org> (raw)
In-Reply-To: <5255E98C.3020009@alteeve.ca>
Good morning,
On 10/09/2013 07:41 PM, Digimer wrote:
> I forgot to add the smartctl output;
>
> /dev/sdb: http://fpaste.org/45627/13813614/
> /dev/sdc: http://fpaste.org/45628/38136150/
> /dev/sdd: http://fpaste.org/45630/36151813/
> /dev/sde: http://fpaste.org/45632/36154613/
>
> (sorry for the top post, worried this would have gotten lost below)
[You could/should have just trimmed the material below.]
Anyways, excellent report.
According to the mdadm -E data, you should only need to perform a forced
assembly, like so:
mdadm --stop /dev/md1
mdadm --assemble --force /dev/md1 /dev/sd[bcde]2
Your drives all have the same event counts, suggesting that they were
all dieing within milliseconds of each other. One of them lived long
enough to record the another's failure, but not to bump the event count.
The dead machine almost certainly suffered a catastrophic hardware failure.
Presuming the forced assembly works, you should plan on tossing these
drives after you get your data... they have dangerously high relocation
counts and cannot be trusted. (Fairly typical for consumer drives
approaching 30k hours.)
HTH,
Phil
next prev parent reply other threads:[~2013-10-10 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 23:25 Broken array, trying to assemble enough to copy data off Digimer
2013-10-09 23:41 ` Digimer
2013-10-10 12:44 ` Phil Turmel [this message]
2013-10-10 16:20 ` Digimer
2013-10-10 16:36 ` Phil Turmel
2013-10-10 16:54 ` Digimer
2013-10-10 17:58 ` Phil Turmel
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=5256A14B.7030008@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lists@alteeve.ca \
/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).