Hello,

 

I had a drive I pulled out of a production RAID5 array and set aside because the drive was marked as failed.  On a wim, I decided to put this in my UNRAID server and run a preclear to see how it fairs.

 

Everything ran perfectly. 

 

0 sectors were pending re-allocaiton before start of preclear

0 sectors were pending re-allocation after pre-read in cycle 1 of 1

0 sectors were pending re-allocation after zero of disk in cycle 1 of 1

0 sectors are pending re-allocaiton a tthe end of the preclear, the number of sectors pending re-allocation did not change.

0 sectors had been re-allocated before the start of the preclear.

0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.

 

Now ...

 

I have the following SMART values that were changed:

** Changed attributes in files: /tmp/smart_start_sdd  /tmp/smart_finish_sdd
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
         Spin_Retry_Count =   100     100           97        near_thresh 0
  Airflow_Temperature_Cel =    35      53           45        FAILING_NOW 65
      Temperature_Celsius =    65      47            0        ok          65
   Hardware_ECC_Recovered =    61     102            0        ok          19629146

*** Failing SMART Attributes in /tmp/smart_finish_sdd ***
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
190 Airflow_Temperature_Cel 0x0022   035   035   045    Old_age   Always   FAILING_NOW 65 (7 12 65 28)

 

Do I really need to worry about these attributes?  I have not added this drive to my array, and my research tells me this attribute is NOT important.  Its too bad that my RAID card (in another server) was this sensitive to flag this drive as failed when it appears to be operating nicely.  Is it safe to add this drive to my array?  I can not send this back to seagate, as this is marked as an OEM drive and was resold to me by Frys as a re manufactured drive.  They only allow a 15 day return on these drives.  That is long past.  If nothing else I will just use this as a USB drive.

 

Thanks for your help.

 

Sideband Samurai

*-Bump-*

I had a similar problem recently, it turned out that I had a memory issue that caused the smart error.  What I did was dropped the drive in a windows machine and used WD drive diagnostic tool and ran an extended test, It failed, then wrote 0's to the drive with the tool (it may have been 1's), it passed, then I reran the extended test and it passed.

 

I then dropped the disk in to my unraid machine and ran a badblock write test, it passed, then finally raid 5 cycles of preclear, it had 0 errors each cycle.  I called the drive good and added it back to the array.

 

If you are uncomfortable of having important data on this drive exclude the disk from important shares, use snap, use it in a different machine, external drive, ect.

 

I use my unRAID as a local back up and for stuff that I don’t care if I lose.  I use crashplan as an offsite backup.  So if my drive really does fail oh well.