I've continued to use this drive despite getting errors when I run parity checks, it seems to work just fine. Here is the latest SMART report. My question is should I be replacing this drive?

 

Thanks guys and sorry for the bump.

smart.txt

198 Offline_Uncorrectable  0x0030  200  200  000    Old_age  Offline      -      18

 

Slowly increasing...I would replace it, maybe overcautious - but if you get 2 drives that fail at the same time...

I went ahead and replaced the drive and decided to run the preclear utility on it to verify problems:

 

1 sector was pending re-allocation before the start of the preclear.

1 sector was 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.

55 sectors are pending re-allocation at the end of the preclear,

a change of 54 in the number of sectors pending re-allocation

0 sectors has 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.

 

I'm assuming the huge increase in re-allocations means this drive is headed for a garbage bin? Or is there a point where it will find all these damaged sectors and start working normally?

 

Smart report now shows:

  1 Raw_Read_Error_Rate    0x002f  200  200  051    Pre-fail  Always      -      141

197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      55

198 Offline_Uncorrectable  0x0030  200  200  000    Old_age  Offline      -      0

 

Looks like it was able to read previous pending sectors, and therefore did not move them to "uncorrectable". You could run additional preclear cycles to see the demise.  Of course, it could clear itself.

 

If you run multiple cycles of preclear, by typing

preclear_disk.sh -c 3 /dev/sdX

steps performed will be

1, 2, 3, 2, 3, 2, 3, 4

http://lime-technology.com/forum/index.php?topic=15110.msg142621#msg142621

 

Looks like it was able to read previous pending sectors, and therefore did not move them to "uncorrectable". You could run additional preclear cycles to see the demise.  Of course, it could clear itself.

 

If you run multiple cycles of preclear, by typing

preclear_disk.sh -c 3 /dev/sdX

steps performed will be

1, 2, 3, 2, 3, 2, 3, 4

http://lime-technology.com/forum/index.php?topic=15110.msg142621#msg142621

 

 

I started another preclear but was unaware of this option, will re-start it with your suggestion. Many thanks!