From: Phil Turmel <philip@turmel.org>
To: Ramon Hofer <ramonhofer@bluewin.ch>
Cc: stan@hardwarefreak.com, linux-raid@vger.kernel.org
Subject: Re: Stacked array data recovery
Date: Mon, 02 Jul 2012 07:46:43 -0400 [thread overview]
Message-ID: <4FF18A23.9060806@turmel.org> (raw)
In-Reply-To: <1341223955.3407.6.camel@hoferr-desktop.hofer.rummelring>
Hi Ramon,
On 07/02/2012 06:12 AM, Ramon Hofer wrote:
> On Die, 2012-06-26 at 15:23 -0500, Stan Hoeppner wrote:
>
>> Regardless, unless the dd commands hung in some way, they should not
>> show up in top right now. So it's probably safe to assume they completed.
>>
>> So at this point you can try creating the RAID5 array again. If the dd
>> command did what we wanted, /dev/sdk should have remapped the bad
>> sector, and you shouldn't get the error kicking that drive. If you
>> still do, you may need to replace the drive.
>
> I have successfully run dd for all the four drives.
>
> But because I couldn't create the raid I ran smartctl again for all of
> them. It seems that sdk has to be replaced. Here are the outputs:
>
> sdj:
> http://pastebin.com/raw.php?i=V60FJ4wC
>
> sdk:
> http://pastebin.com/raw.php?i=cgfq3202
> There are some pre-fail and one FAILING_NOW messages.
Absolutely take this drive back to your dealer. It has re-allocated
over a thousand sectors. In my opinion, a drive should be put on a
short-term (~3month) replacement list for the next convenient
opportunity as soon as the first sector gets relocated. If you get more
relocations in quick succession, replace immediately.
> sdl:
> http://pastebin.com/raw.php?i=tipjbpxu
Interesting. This drive claims to support SCTERC. I was under the
impression the EARS drives didn't. Could you please show the output of
"smartctl -l scterc /dev/sdl" ?
Regards,
Phil
next prev parent reply other threads:[~2012-07-02 11:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 22:44 Stacked array data recovery Ramon Hofer
2012-06-22 14:32 ` Ramon Hofer
2012-06-23 12:05 ` Stan Hoeppner
2012-06-22 14:37 ` Ramon Hofer
2012-06-23 12:09 ` Stan Hoeppner
2012-06-24 12:15 ` Ramon Hofer
2012-06-24 14:12 ` Stan Hoeppner
2012-06-25 3:51 ` Stan Hoeppner
2012-06-25 10:31 ` Ramon Hofer
2012-06-26 1:53 ` Stan Hoeppner
2012-06-26 8:37 ` Ramon Hofer
2012-06-26 20:23 ` Stan Hoeppner
2012-06-27 9:07 ` Ramon Hofer
2012-06-27 12:34 ` Stan Hoeppner
2012-06-27 19:19 ` Ramon Hofer
2012-06-28 19:57 ` Stan Hoeppner
2012-06-29 7:58 ` Ramon Hofer
2012-06-28 18:44 ` Krzysztof Adamski
2012-06-29 7:44 ` Ramon Hofer
2012-06-29 10:15 ` John Robinson
2012-06-29 11:19 ` Ramon Hofer
2012-07-02 10:12 ` Ramon Hofer
2012-07-02 11:46 ` Phil Turmel [this message]
2012-07-02 12:18 ` Ramon Hofer
2012-07-02 21:42 ` Phil Turmel
2012-07-02 20:27 ` Stan Hoeppner
2012-07-03 7:16 ` Ramon Hofer
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=4FF18A23.9060806@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=ramonhofer@bluewin.ch \
--cc=stan@hardwarefreak.com \
/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.