From: Brad Campbell <brad@fnarfbargle.com>
To: Anssi Hannula <anssi.hannula@iki.fi>
Cc: Jan Ceuleers <jan.ceuleers@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Preventative replacement of active RAID1 disks
Date: Sun, 22 Jan 2012 00:50:00 +0800 [thread overview]
Message-ID: <4F1AECB8.6020905@fnarfbargle.com> (raw)
In-Reply-To: <4F1AE34D.8030209@iki.fi>
On 22/01/12 00:09, Anssi Hannula wrote:
> On 18.01.2012 19:04, Jan Ceuleers wrote:
>> List,
>>
>> I have two 2-partition RAID1 sets, each with a spare. The SMART info for
>> both active disks suggests that I should replace them. Both of them. I
>> based this on the Seek_Error_Rate in the smartctl -a output (below).
> [...]
>> Model Family: Seagate Barracuda 7200.12 family
>> Device Model: ST3500418AS
>> 7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail
>> Always - 93484948
> [...]
>> Model Family: Seagate Barracuda 7200.12 family
>> Device Model: ST3500418AS
>> 7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail
>> Always - 97304022
> [...]
>
> I don't think these indicate any issue with the drives, all of my
> Seagate disks have random big values in that attribute (from 11717390 to
> 103488378525).
>
The only use you get from the Seek_Error_Rate is if you have multiple of the same drive, with the
same firmware in the same environment. You can then look for any outliers. I had this with 30 Maxtor
Maxline-II drives, and looking at the seek error rates across the drives gave you a pretty good
indicator of a drive that was in trouble as its count varied wildly from that of its siblings. Raw
counts like that are manufacturer/family/firmware specific and in isolation mean nothing to the layman.
If you've got no reallocations, SMART tells you the drive is ok and you are not noticing any odd
behaviour the chances of the drive being in distress are pretty slim.
next prev parent reply other threads:[~2012-01-21 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 17:04 Preventative replacement of active RAID1 disks Jan Ceuleers
2012-01-21 16:09 ` Anssi Hannula
2012-01-21 16:50 ` Brad Campbell [this message]
2012-01-21 17:21 ` Wolfgang Denk
2012-01-21 17:01 ` Jan Ceuleers
2012-01-29 8:43 ` Jan Ceuleers
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=4F1AECB8.6020905@fnarfbargle.com \
--to=brad@fnarfbargle.com \
--cc=anssi.hannula@iki.fi \
--cc=jan.ceuleers@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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.