linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: Gavin Flower <gavinflower@yahoo.com>, linux-raid@vger.kernel.org
Subject: Re: RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive
Date: Fri, 15 Apr 2011 00:15:00 +0100	[thread overview]
Message-ID: <4DA77FF4.7030007@anonymous.org.uk> (raw)
In-Reply-To: <BANLkTinttwOaDm=QK5nbUd6Vbfzwur1Lyw@mail.gmail.com>

On 14/04/2011 22:19, Mathias Burén wrote:
> On 14 April 2011 22:14, Gavin Flower<gavinflower@yahoo.com>  wrote:
[...]
>> Attaching OpenDocument file with full details of smart output and comparison table.
[...]
> sda has a value higher than 0 on reported uncorrected sectors. That's
> enough for me to replace a drive. (heck, even if I see 1 reallocated
> sector I'd RMA it ASAP).

I've had a look at some of my drives' SMART output, and only my Samsung 
drives have it - one showing 57 (with zero reallocated, pending or 
offline sectors) and one showing 331 (zero reallocated, one pending and 
zero offline sectors). Neither drive has ever given a read error, and I 
do run a weekly check on my arrays which has never reported any mismatches.

Googling for this field doesn't give any indication that it is relevant 
to determining whether a drive is failing, but if someone with more 
SMART expertise can comment I'll be quite happy to be corrected...

Having said that, all of Gavin's drives apart from sdc show non-zero 
reallocated sector counts, and that field definitely is one to follow 
when considering replacing drives.

Cheers,

John.
(Just started long self-tests on all my local drives)

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-04-14 23:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 21:14 RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive Gavin Flower
2011-04-14 21:19 ` Mathias Burén
2011-04-14 23:15   ` John Robinson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-13 22:24 Gavin Flower
2011-04-13 22:28 ` Mathias Burén
2011-04-14  0:15   ` Gavin Flower
2011-04-14  4:08     ` Roman Mamedov
2011-04-14 13:16     ` Phil Turmel
2011-04-14 21:12       ` Gavin Flower
2011-04-14 22:23         ` Phil Turmel
2011-04-28 20:03           ` Gavin Flower
2011-04-28 20:11             ` Roman Mamedov
2011-04-28 22:11               ` Phil Turmel
2011-04-28 22:40                 ` Phil Turmel
2011-04-13 23:09 ` NeilBrown
2011-04-08  2:01 Gavin Flower
2011-04-08  1:34 Gavin Flower
2011-04-08  1:32 Gavin Flower
2011-04-08  9:34 ` NeilBrown
2011-04-08  9:59   ` Gavin Flower
2011-04-08 11:50     ` NeilBrown
2011-04-11  6:50       ` Gavin Flower
2011-04-12 21:30       ` Gavin Flower
2011-04-13 10:57         ` John Robinson
2011-04-13 11:13           ` NeilBrown
2011-04-13 11:58             ` John Robinson
2011-04-13 20:30               ` Gavin Flower
2011-04-07 21:58 Gavin Flower

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=4DA77FF4.7030007@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=gavinflower@yahoo.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mathias.buren@gmail.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).