From: Ramon Hofer <ramonhofer@bluewin.ch>
To: stan@hardwarefreak.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Stacked array data recovery
Date: Tue, 03 Jul 2012 09:16:06 +0200 [thread overview]
Message-ID: <1341299766.3437.6.camel@hoferr-desktop.hofer.rummelring> (raw)
In-Reply-To: <4FF2043A.4060505@hardwarefreak.com>
On Mon, 2012-07-02 at 15:27 -0500, Stan Hoeppner wrote:
> On 7/2/2012 5: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:
>
> > sdk:
> > http://pastebin.com/raw.php?i=cgfq3202
>
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> ...
> 5 Reallocated_Sector_Ct 0x0033 133 133 140 Pre-fail Always FAILING_NOW 1265
> 7 Seek_Error_Rate 0x002e 103 103 000 Old_age Always - 15797
> 196 Reallocated_Event_Count 0x0032 142 142 000 Old_age Always - 58
> 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 14
> 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 15
> 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 15
>
> Yes, the drive is toast. Above are the indicators. IIRC, your previous smartctl run showed only a count of 3 for Current_Pending_Sector, but no other errors. Zero'ing the drive with dd has uncovered the true severity of the drive's problems, as another 1000+ bad sectors were identified by the drive and remapped.
>
> So yes, the drive needs to be replaced.
Thanks for the explanation!
I brought the drive to my dealer yesterday and could take a new one with
me. :-)
I only had to pay the difference of CHF 10.-
Btw Stan: I wrote to the manufacturer of the damping mats. He told me
that they are isolating. I asked about the value of resistance and if
it's flammable. When I have the answer I will order them...
Cheers
Ramon
prev parent reply other threads:[~2012-07-03 7:16 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
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 [this message]
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=1341299766.3437.6.camel@hoferr-desktop.hofer.rummelring \
--to=ramonhofer@bluewin.ch \
--cc=linux-raid@vger.kernel.org \
--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 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).