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 17:42:09 -0400 [thread overview]
Message-ID: <4FF215B1.4070105@turmel.org> (raw)
In-Reply-To: <1341231520.3449.4.camel@hoferr-desktop.hofer.rummelring>
On 07/02/2012 08:18 AM, Ramon Hofer wrote:
> Ok, thanks!
> I will bring it back.
>
> I've never had to replace a disk so far. Does it depend on the dealer or
> do the manufacturers replace them already when sectors get reallocated?
I don't know--I've never had an in-service drive fail while still under
warranty :-) I did have a DOA replaced once, but I doubt that reflects
the hoops you might have to jump through. Maybe just send them the
smartctl report?
As a hobbyist and small businessman, I only run my own servers. I don't
handle the volume of drives necessary to personally know the RMA
departments.
Others around here probably do.
>> 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" ?
>
> Sure:
>
> ~# smartctl -l scterc /dev/sdl
> smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
> Copyright (C) 2002-10 by Bruce Allen,
> http://smartmontools.sourceforge.net
>
> Error SMART WRITE LOG does not return COUNT and LBA_LOW register
> Warning: device does not support SCT (Get) Error Recovery Control
> command
Very interesting indeed. The summary report says it *does* support
SCTERC, but when actually probed, it refuses. That's just evil.
Thanks for running the query.
Regards,
Phil
next prev parent reply other threads:[~2012-07-02 21:42 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 [this message]
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=4FF215B1.4070105@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.