From: "Stefan G. Weichinger" <lists@xunil.at>
To: Roman Mamedov <roman@rm.pp.ru>
Cc: st0ff@npl.de, st0ff@gmx.net, Tim Small <tim@seoss.co.uk>,
linux-raid@vger.kernel.org
Subject: Re: Pending sectors in valid array - how to proceed?
Date: Thu, 29 Jul 2010 10:45:01 +0200 [thread overview]
Message-ID: <4C513F8D.5000604@xunil.at> (raw)
In-Reply-To: <20100729031100.69f583d7@natsu>
Am 28.07.2010 23:11, schrieb Roman Mamedov:
> 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.
Yep, it's a Seagate.
All four are Seagate:
sda, sdb: ST3250310NS (should have ERC as far as I found online)
sdc, sdd: ST3250621NS (still don't know if they have ERC)
I now decided to run that check-action on all three arrays.
So far it looks good. All three arrays re-synced OK, without any drive
failing. Good :-)
Still no reallocated sectors on all four drives.
"Current_Pending_Sector" and "Offline_Uncorrectable" on /dev/sdb still
at the old value of "13".
Do you think I should swap that drive or not?
(added difficulty: that server is around 400km from me ... I would have
to direct an employee there to swap the hdd ...)
Migrating to RAID6, sure, would make sense, but this would need a
kernel-upgrade and involves quite some work. Right now I have
2.6.25-gentoo-r7 there :-(
thank you all for your replies, Stefan
prev parent reply other threads:[~2010-07-29 8:45 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
2010-07-29 2:50 ` Simon Matthews
2010-07-30 4:24 ` Simon Matthews
2010-07-29 8:45 ` Stefan G. Weichinger [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=4C513F8D.5000604@xunil.at \
--to=lists@xunil.at \
--cc=linux-raid@vger.kernel.org \
--cc=roman@rm.pp.ru \
--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;
as well as URLs for NNTP newsgroup(s).