possible hardware failure ?

Claudiu dr.clau at rdslink.ro
Sun Aug 22 02:06:53 PDT 2004


I have also checked the SMART state of the driver with smartctl, it 
looks like this:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE 
UPDATED  WHEN_FAILED RAW_VALUE
   1 Raw_Read_Error_Rate     0x000f   062   056   006    Pre-fail 
Always       -       101410838
   3 Spin_Up_Time            0x0003   096   096   000    Pre-fail 
Always       -       0
   4 Start_Stop_Count        0x0032   100   100   020    Old_age 
Always       -       0
   5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail 
Always       -       0
   7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail 
Always       -       146351689
   9 Power_On_Hours          0x0032   094   094   000    Old_age 
Always       -       5292
  10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail 
Always       -       0
  12 Power_Cycle_Count       0x0032   100   100   020    Old_age 
Always       -       67
194 Temperature_Celsius     0x0022   034   047   000    Old_age   Always 
       -       34
195 Hardware_ECC_Recovered  0x001a   062   056   000    Old_age   Always 
       -       101410838
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always 
       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age 
Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always 
       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age 
Offline      -       0
202 TA_Increase_Count       0x0032   100   253   000    Old_age   Always 
       -       0


This does not look very encouraging, but seems to be in reasonable limits.
I have 2 drivers, and I am using vinum for mirroring. Both are in 
similar situation.
Should I trust both of them until the SMART attributes are closer to to 
the WORST case ?


Best regards,

-- 
Claudiu Dragalina-Paraipan
e-mail: dr.clau at rdslink.ro



More information about the freebsd-hackers mailing list