From: Mike Hardy <mhardy@h3c.com>
To: Konstantin Olchanski <olchansk@sam.triumf.ca>
Cc: Harry Mangalam <hjm@tacgi.com>, linux-raid@vger.kernel.org
Subject: Re: SMART, was Re: More tales of horror from the linux (HW) raid crypt
Date: Wed, 22 Jun 2005 16:35:10 -0700 [thread overview]
Message-ID: <42B9F5AE.7040305@h3c.com> (raw)
In-Reply-To: <20050622231513.GC23624@sam.triumf.ca>
Konstantin Olchanski wrote:
> But does anybody know what all these SMART parameters *mean* ?!?
>
> What is this "Raw_Read_Error_Rate"?
> What is this "Seek_Error_Rate"?
Most of them seem to make sense.
I'd guess raw read error rate is the number of read errors corrected by
the firmware in some way (recalibration, ecc, or something).
Seek error rate is probably a calibration thing. The last time I googled
one, I got a pretty good answer.
This was the site I saw:
http://www.ariolic.com/activesmart/smart-attributes/soft-read-error-rate.html
> Then for the SMART "status", it is completely useless- I had SMART
> complain about perfectly good disks ("this disk will fail soon!!!"- a few
> 120GB WDs that sometimes stop seeking, probably through overheating)
> and I had completely unusable disks (i.e. develops about 10 unreadable
> sectors per day) that SMART was perfectly happy with.
Well, I guess anecdotal evidence is just that. At least for the mostly
Maxtor drives I run (which do fail from time to time, alas), the SMART
monitoring has been dead on. Every time. If there's a bad block, SMART
sees it. Right before the drive goes belly-up mysteriously, I'll get
lots of soft read error rate triggers or TA increase count triggers etc.
Its gotten to where if its not a bad block, I should just about hook it
up with an automated dealtime.com query to just buy a drive.
I imagine most folks are somewhere in between. I'm never going to run a
drive without smartd watching it again though, that's for sure.
-Mike
next prev parent reply other threads:[~2005-06-22 23:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 11:47 when does it become faulty disk Raz Ben-Jehuda(caro)
2005-06-19 19:10 ` Molle Bestefich
2005-06-20 6:43 ` raz ben jehuda
2005-06-20 7:55 ` Molle Bestefich
2005-06-20 10:09 ` raz ben jehuda
2005-06-20 13:45 ` Michael Tokarev
2005-06-20 15:35 ` raz ben jehuda
2005-06-21 1:53 ` More tales of horror from the linux (HW) raid crypt Harry Mangalam
2005-06-22 19:33 ` Mike Hardy
2005-06-22 20:16 ` Harry Mangalam
2005-06-22 20:38 ` Jure Pecar
2005-06-22 21:33 ` Harry Mangalam
2005-06-22 23:15 ` SMART, was " Konstantin Olchanski
2005-06-22 23:32 ` Harry Mangalam
2005-06-22 23:35 ` Mike Hardy [this message]
2005-06-22 21:09 ` Brad Dameron
2005-06-22 21:43 ` Harry Mangalam
2005-06-22 22:00 ` Ming Zhang
2005-06-22 22:11 ` John Madden
2005-06-22 22:26 ` Ming Zhang
2005-06-23 0:20 ` bdameron
2005-06-22 22:45 ` Harry Mangalam
2005-06-22 23:05 ` Ming Zhang
2005-06-23 0:25 ` bdameron
2005-06-23 0:14 ` bdameron
2005-06-23 0:49 ` Ming Zhang
2005-06-23 3:05 ` Guy
2005-06-23 12:31 ` Ming Zhang
2005-06-23 13:03 ` Guy
2005-06-23 13:17 ` Andy Smith
2005-06-23 13:19 ` Ming Zhang
2005-06-22 23:54 ` Jon Lewis
2005-06-22 20:54 ` Dan Stromberg
2005-06-22 21:15 ` Brad Dameron
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=42B9F5AE.7040305@h3c.com \
--to=mhardy@h3c.com \
--cc=hjm@tacgi.com \
--cc=linux-raid@vger.kernel.org \
--cc=olchansk@sam.triumf.ca \
/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).