From: Roman Mamedov <roman@rm.pp.ru>
To: st0ff@npl.de
Cc: st0ff@gmx.net, Tim Small <tim@seoss.co.uk>,
lists@xunil.at, linux-raid@vger.kernel.org
Subject: Re: Pending sectors in valid array - how to proceed?
Date: Thu, 29 Jul 2010 03:11:00 +0600 [thread overview]
Message-ID: <20100729031100.69f583d7@natsu> (raw)
In-Reply-To: <4C5092C4.6050708@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
On Wed, 28 Jul 2010 22:27:48 +0200
Stefan *St0fF* Huebner <st0ff@gmx.net> wrote:
> >> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always
> >> - 0
> >> 195 Hardware_ECC_Recovered 0x001a 058 039 000 Old_age Always
> >> - 146754005
> >> 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
> >> - 13
> >> 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
> >> Offline - 13
> >>
> >> (relevant lines as far as I understand ...)
> >>
> > Do you have any high-fly writes? Are there lots of
> > Hardware_ECC_Recovered on all the drives? Is vibration likely to be an
> > issue? What's the drive/chassis?
> Hardware ECC recovered means how many times the internal error
> correction of the drive succeeded. Indeed this may indicate vibration
> or other external sources of errors.
That drive is most likely a Seagate, and if so, there's nothing to worry
about. Literally every Seagate drive will have a high value in
Hardware_ECC_Recovered, it's just a peculiarity of their SMART. Other vendors'
drives recover read errors using ECC too, but don't report that into the SMART
metric.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-07-28 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 17:46 Pending sectors in valid array - how to proceed? Stefan G. Weichinger
2010-07-28 18:41 ` Tim Small
2010-07-28 20:27 ` Stefan *St0fF* Huebner
2010-07-28 21:11 ` Roman Mamedov [this message]
2010-07-29 2:50 ` Simon Matthews
2010-07-30 4:24 ` Simon Matthews
2010-07-29 8:45 ` Stefan G. Weichinger
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=20100729031100.69f583d7@natsu \
--to=roman@rm.pp.ru \
--cc=linux-raid@vger.kernel.org \
--cc=lists@xunil.at \
--cc=st0ff@gmx.net \
--cc=st0ff@npl.de \
--cc=tim@seoss.co.uk \
/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