Think i have a Failed Drive?

[pantner]

Here is the smart report for one of my 2TB Seagate LP drives

 

Now, im not the best at reading these (ie, do i look at raw value or value/worst), but i think 1 & 7 are very bad.

 

Just looking for confirmation.

 

The drive gives errors in UnRaid

smart.txt

[Joe L.]

Here is the smart report for one of my 2TB Seagate LP drives

 

Now, im not the best at reading these (ie, do i look at raw value or value/worst), but i think 1 & 7 are very bad.

 

Just looking for confirmation.

 

The drive gives errors in UnRaid

You look at the current normalized value compared to its corresponding failure threshold.

The failure threshold for "1" is "006" and the current value is "117", the worst in the past was "099" .  Both are higher than the failure threshold.  The manufacturer therefore thinks its raw-read-error-rate is within limits.

 

The failure threshold for "7" is "030" and the current value is "078" so again, it is within the limits set by the manufacturer.

 

(All drives have raw-read-errors.  Some report them, some do not unless the re-read fails.  The RAW column for many columns is meaningless to anybody but the manufacturer, and they don't tell anyone how to interpret them.  To illustrate, look at the raw column for "head-flying-hours"  Its value is "156740536507884".  Even if that was millionths of a second, it would represent 4,966.9 years.  I doubt the disk has been spinning that long. )

 

According to the SMART report, the disk has not failed.  That could easily point to cabling picking up induced noise, or a marginal power supply.

 

You need to post a syslog showing how unRAID is seeing and reacting to the errors.  (It might be resetting the disk controller any making subsequent attempts to get to the data)  Only that will tell you what is actually happening now that nothing is glaringly bad in the SMART report.

 

Joe L.

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   117   099   006    Pre-fail  Always       -       161537528
  3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       269
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail  Always       -       8716440144
  9 Power_On_Hours          0x0032   091   091   000    Old_age   Always       -       8179
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       267
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   086   000    Old_age   Always       -       85900656661
189 High_Fly_Writes         0x003a   097   097   000    Old_age   Always       -       3
190 Airflow_Temperature_Cel 0x0022   062   053   045    Old_age   Always       -       38 (Lifetime Min/Max 32/46)
194 Temperature_Celsius     0x0022   038   047   000    Old_age   Always       -       38 (0 14 0 0)
195 Hardware_ECC_Recovered  0x001a   051   027   000    Old_age   Always       -       161537528
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       -       12
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       156740536507884
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3788806164
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       1897357696

[pantner]

Thanks for the reply.

 

Will try changing the SATA cable when i get home.

 

However, i do think there is something going on with the drive.

 

The drive is in a hotswap cage and the status light for the drive is orange. If i move the drive to another tray (and therefor another sata cable) the orange light follows the drive.

 

I was also doing a full seatools for windows test, i left the machine too long and the drive went into standby, when it spun up the computer bluescreened.

Will be doing that again soon (maybe tonight).

 

I will turn on my array again and see what happens, if there are errors i will post my syslog.

[pantner]

well, going with my gut, i bought a new Seagate 2TB drive on the way home (if the drive is ok i just expanded my array by 2TB )

 

so far everything is good.

 

The light on my hotswap cage is now green instead of yellow and when i left for work this morning the drive had almost finished 1 preclear run.

The 2TB here got to step 2 and then said "This drive cannot complete a preclear" or something similar.

 

Ran a full seatools test overnight and it passed ( )

Started a second one before work, will check it today.

If it passes i will do a full format and see if that errors, i have a feeling the problem might present when writing to the drive as (i think) step 2 of the preclear process is writing to the drive but step 1 is just reading?