I just noticed that i have 35 errors on my parity drive.  I accidently cleared the notifications so i couldn't figure out when it happened.  I did have a parity check done on 7/1, and it completed and says with 0 errors.  I ran an extended smart test (i think it took about 6-8hrs) and i've attached it along with a diagnostic.  

The smart test said that it completed without errors.  

Is this something to worry about? 

tower-diagnostics-20200707-2029.zip tower-smart-20200707-1554.zip

Those are real error, SMART also record it, the last one at 30703 hrs and next few on 29985 hrs.

This indicate disk not reliable or going to be fault, even it pass extended-test.

 

Error 17 [16] occurred at disk power-on lifetime: 30703 hours (1279 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

 

Error 16 [15] occurred at disk power-on lifetime: 29985 hours (1249 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

 

Error 15 [14] occurred at disk power-on lifetime: 29985 hours (1249 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

Edited July 8, 20205 yr by Benson

It does look like a genuine problem, both these attributes should be 0 on a healthy WD drive:

 

ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    68
  200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    24

But these error can be intermittent, also confirmed by the SMART test passing, but likely there will be more errors in the near future, together with those attributes increasing, if they remain stable disk still might be good for some time.

7 hours ago, johnnie.black said:

It does look like a genuine problem, both these attributes should be 0 on a healthy WD drive:

 

ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    68
  200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    24

But these error can be intermittent, also confirmed by the SMART test passing, but likely there will be more errors in the near future, together with those attributes increasing, if they remain stable disk still might be good for some time.

Thanks!  I'm running dual parity, so that good, and i've got a record of it now so i can watch it to see if it increases at all.  I think i'll grab a fresh drive just to be safe.  

9 hours ago, Benson said:

Those are real error, SMART also record it, the last one at 30703 hrs and next few on 29985 hrs.

This indicate disk not reliable or going to be fault, even it pass extended-test.

 

Error 17 [16] occurred at disk power-on lifetime: 30703 hours (1279 days + 7 hours)
  When the command that caused the error occurred, the device was active or idle.

 

Error 16 [15] occurred at disk power-on lifetime: 29985 hours (1249 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

 

Error 15 [14] occurred at disk power-on lifetime: 29985 hours (1249 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

interesting that it happened 30 days apart, and thats when i have my parity check done.  Just a coincidence?

4 minutes ago, danimal86 said:

Just a coincidence?

No, parity check reads the entire disk surface, so if there are errors they're bound to show up during it.

1 minute ago, johnnie.black said:

No, parity check reads the entire disk surface, so if there are errors they're bound to show up during it.

gotcha.  Thanks for the info. 

I'm on the hunt for a backup.  i was thinking about getting a refurb hgst drive, but i think for the parity, i'll try to get something brand new.