From: Konstantin Olchanski <olchansk@sam.triumf.ca>
To: Harry Mangalam <hjm@tacgi.com>
Cc: linux-raid@vger.kernel.org
Subject: SMART, was Re: More tales of horror from the linux (HW) raid crypt
Date: Wed, 22 Jun 2005 16:15:13 -0700 [thread overview]
Message-ID: <20050622231513.GC23624@sam.triumf.ca> (raw)
In-Reply-To: <200506221433.00321.hjm@tacgi.com>
On Wed, Jun 22, 2005 at 02:33:00PM -0700, Harry Mangalam wrote:
> The SMART data ... would tell you considerably more info:
> an example from my home system:
> 1062 $ smartctl -a /dev/hda ...
But does anybody know what all these SMART parameters *mean* ?!?
What is this "Raw_Read_Error_Rate"?
What is this "Seek_Error_Rate"?
AFAIK, only a handful of parameters ("temperature", "reallocated sectors",
and "start stop count") seem to measure something. All the other
stuff appears to be complete gibberish.
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.
K.O.
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
> WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000b 200 200 051 Pre-fail Always
> - 0
> 3 Spin_Up_Time 0x0007 099 095 021 Pre-fail Always
> - 4141
> 4 Start_Stop_Count 0x0032 100 100 040 Old_age Always
> - 122
> 5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always
> - 2
> 7 Seek_Error_Rate 0x000b 200 200 051 Pre-fail Always
> - 0
> 9 Power_On_Hours 0x0032 075 075 000 Old_age Always
> - 18940
> 10 Spin_Retry_Count 0x0013 100 100 051 Pre-fail Always
> - 0
> 11 Calibration_Retry_Count 0x0013 100 100 051 Pre-fail Always
> - 0
> 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always
> - 120
> 196 Reallocated_Event_Count 0x0032 198 198 000 Old_age Always
> - 2
> 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always
> - 0
> 198 Offline_Uncorrectable 0x0012 200 200 000 Old_age Always
> - 0
> 199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always
> - 0
> 200 Multi_Zone_Error_Rate 0x0009 200 200 051 Pre-fail Offline
> - 0
>
> SMART Error Log Version: 1
> No Errors Logged
>
>
> On Wednesday 22 June 2005 1:38 pm, Jure Pecar wrote:
> > On Wed, 22 Jun 2005 13:16:33 -0700
> >
> > Harry Mangalam <hjm@tacgi.com> wrote:
> > > Perhaps something like the CDDB, where a you can run an applet on a
> > > cronjob that will upload your disk's SMART data cache to a remote DB on
> > > a regular basis, so the millions of disks out there can be profiled.
> > > Hmmm - sounds like a good undergrad project. Did someone say Summer of
> > > Code? (http://code.google.com/summerofcode.html)
> >
> > Actually if you look at the storagereview.com, they already have a crude
> > form of this online under "reliability survey". You have to login, then you
> > can enter disk model that you have expirience with and what were those
> > expiriences. There's quite some info already available ...
>
> --
> Cheers, Harry
> Harry J Mangalam - 949 856 2847 (vox; email for fax) - hjm@tacgi.com
> <<plain text preferred>>
> -
> 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
--
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
next prev parent reply other threads:[~2005-06-22 23:15 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 ` Konstantin Olchanski [this message]
2005-06-22 23:32 ` SMART, was " Harry Mangalam
2005-06-22 23:35 ` Mike Hardy
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=20050622231513.GC23624@sam.triumf.ca \
--to=olchansk@sam.triumf.ca \
--cc=hjm@tacgi.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 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).