Disk

JD jd1008 at gmail.com
Mon Nov 26 00:44:19 UTC 2012


On 11/25/2012 09:27 AM, Robert Nichols wrote:
> On 11/24/2012 10:27 PM, JD wrote:
>> Here are the values for #197
>> ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
>> For sdb:
>> 1 Raw_Read_Error_Rate POSR-- 117 099 006 - 131606848
>> 197 Current_Pending_Sector -O--C- 100 100 000 - 0
>> For sdc:
>> 1 Raw_Read_Error_Rate POSR-- 114 069 006 - 80733495
>> 197 Current_Pending_Sector -O--C- 100 100 000 - 0
>>
>>
>> If the raw read error values are so high, and the normalized values
>> for raw read error rate exceeds worst case value, does that mean the
>> drive dying or near death?
>
> Not at all.  First, suspiciously high "raw" numbers can't always be taken
> at face value.  Seagate in particular likes to pack more than one number
> into that variable, frequently the total number of operations in addition
> to the error count, so you have to trust the normalized values, or
> perhaps go Googling for info on that raw value for your particular drive
> model.  Second, for the normalized values, higher is better.  A failure
> is indicated by a normalized value that is at or below the threshold.
>
> None of the SMART Attributes Data you have posted indicate any serious
> problem with the drives.
>
Thank you Robert!
I truly appreciate your help, as I was about to plunk down a few hundred
bucks to get the NS series seage 3TB drives to replace my drives.

Best regards,

JD


More information about the users mailing list