Put a Drive Back into Production?

[wah00kid]

So one of my zpools ended up dropping a drive for offline uncorrectable sectors.

Its last SMART run from just one day previous to being dropped from the pool was this:

Code:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   112   084   006    Pre-fail  Always       -       156198536
  3 Spin_Up_Time            0x0003   093   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       175
  5 Reallocated_Sector_Ct   0x0033   097   097   010    Pre-fail  Always       -       3376
  7 Seek_Error_Rate         0x000f   079   060   030    Pre-fail  Always       -       92250112
  9 Power_On_Hours          0x0032   062   062   000    Old_age   Always       -       33711
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       159
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   095   095   000    Old_age   Always       -       5
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       1 1 1
189 High_Fly_Writes         0x003a   087   087   000    Old_age   Always       -       13
190 Airflow_Temperature_Cel 0x0022   058   051   045    Old_age   Always       -       42 (Min/Max 26/46)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       74
193 Load_Cycle_Count        0x0032   082   082   000    Old_age   Always       -       37911
194 Temperature_Celsius     0x0022   042   049   000    Old_age   Always       -       42 (0 15 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       32
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       32
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       30371h+35m+10.247s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       41006936486
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       499390039858

So I pulled it put a different drive in and re-sliver and no problems.

I like to take bad drives and run badblocks on them and every other time get loads (way more) bad blocks and chuck the drives.

But this time, I took the drive and then on another machine run badblocks and get this:

Code:

sudo badblocks -b 4096 -ws /dev/sdc
Testing with pattern 0xaa: done                                                 
Reading and comparing: done                                                 
Testing with pattern 0x55: done                                                 
Reading and comparing: done                                                 
Testing with pattern 0xff: done                                                 
Reading and comparing: done                                                 
Testing with pattern 0x00: done                                                 
Reading and comparing: done                                 

No errors! So I run one more long SMART test after badblocks and get this:

Code:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   119   084   006    Pre-fail  Always       -       232554200
  3 Spin_Up_Time            0x0003   093   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       176
  5 Reallocated_Sector_Ct   0x0033   096   096   010    Pre-fail  Always       -       5232
  7 Seek_Error_Rate         0x000f   079   060   030    Pre-fail  Always       -       92491636
  9 Power_On_Hours          0x0032   062   062   000    Old_age   Always       -       33810
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       160
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   086   086   000    Old_age   Always       -       14
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       1 1 3
189 High_Fly_Writes         0x003a   084   084   000    Old_age   Always       -       16
190 Airflow_Temperature_Cel 0x0022   071   051   045    Old_age   Always       -       29 (Min/Max 19/36)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       75
193 Load_Cycle_Count        0x0032   082   082   000    Old_age   Always       -       37912
194 Temperature_Celsius     0x0022   029   049   000    Old_age   Always       -       29 (0 15 0 0 0)
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
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       30470h+45m+04.735s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       64469939225
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       523657337116

So given that the data in this pool is 3 times redundant (the pool (4x3tb,raidz2), a single hard drive in htpc with same data, and an external usb drive with a copy of data) what should I expect from this drive, anyone had any similar experiences with drives. Did badblocks fix this drive?

Thoughts on this? Any other stress testing I could do to punish this thing before putting it back in a pool?

 

[Gen8 Runner]

Which drive is it?

If an enterprise (HSGT or something like that), i would try to get a RMA and change the drive for a new one. Often the manufactures ask you for a test with their own tools and to send you the results of those tests. Then they decide, if it is an RMA or not.

If you have no warranty anymore, i would do some other long-term tests on a different machine and then make my decision about using it as spare again or not.

But in general, almost 4 years non-stop use is (if not enterprise) already close to it's expected time of life. So, don't be sad to say good-bye, especially if it just was a desktop-hdd or a normal WD Red, Ironwolf (non-pro) or something like that.

 

[wah00kid]

Thanks Gen8!

It's a desktop Seagate so yeah I've definitely got my money out of it and no warranty left.

I am wondering what the other long tests are that I could run.

Beyond badblocks what else? I'm happy to set it up on my testrig and run some tests for days.

Would you say this drive is more risky running 24x7 or should I use it as another offline USB external backup where it doesn't run at all and sits on a shelf in case of failure.

It seems silly to chuck it with no errors right now on it.

What's time to a hog as my grandpa said.

 

[Gen8 Runner]

Well, there are several burn in tests for FreeNAS, which many users here use for new HDD's to check, if they are maybe DOA.

With this age, consumer hardware level and that it already was kicked out of the raid, i would honestly not use it anymore for 24/7. Better just as second backup-option and even that with being careful! ;)

It really did it job and i think it is slowly time to say goodbye.