Parity Check Errors

[rowid_alex]

Hello,

 

I am new to unRAID. Yesterday I noticed that the parity check is finished with 13 errors (the previous one 3~5 days before was finished w/o error). All disks are green in my array. I checked SMART data in all disks for 5, 196. 197, 198, and 199 and all healthy. 

Should I be worry about the parity check report or not?

 

Attached is the diagnostic file.

 

Thanks.

 

Best Regards,

Alex

 

unraid-diagnostics-20171006-1756.zip

[JorgeB]

5 minutes ago, rowid_alex said:

Should I be worry about the parity check report or not?

 

Normal to have some errors after this:

 

Oct  5 21:38:57 UNRAID emhttpd: unclean shutdown detected

Unclean shutdowns should be avoided.

[rowid_alex]

29 minutes ago, johnnie.black said:

 

Normal to have some errors after this:

 

Oct  5 21:38:57 UNRAID emhttpd: unclean shutdown detected

Unclean shutdowns should be avoided.

 

Thanks for the reply. That's due to a hang situation of unRAID after I started up a Win10 VM. I had to hardly reboot the tower. I am in a pre-release version so it might be not stable as the stable version. Will try to avoid this in the future.

[rowid_alex]

Hello,

 

Today I did parity check again and still found 51 errors by the end. Since last parity check I don't have any unsafe shutdown. SMART data are all green. Should I worry about this or this is somehow normal?

 

Diagnostics info attached.

 

Thanks.

 

Best Regards,

Alex

 

 

unraid-diagnostics-20171023-2139.zip

[JorgeB]

21 minutes ago, rowid_alex said:

Should I worry about this or this is somehow normal?

 

It's not normal, the only acceptable number of sync errors is 0, start by running memtest, ideally for 24H.

[rowid_alex]

6 minutes ago, johnnie.black said:

 

It's not normal, the only acceptable number of sync errors is 0, start by running memtest, ideally for 24H.

 

Thanks for the quick reply. However I am a bit lost that why I have to run memtest?

 

BTW, in the boot menu of unRAID I have run memtest before, it may take about 40mins and over without any error. How could I let it run for 24 hours?

 

Best Regards,

Alex

[JorgeB]

1 minute ago, rowid_alex said:

However I am a bit lost that why I have to run memtest?

 

To see if there are any memory errors, though memtest doesn't always find them.

 

1 minute ago, rowid_alex said:

it may take about 40mins and over without any error

 

Not enough, even 24h may not be enough.

[rowid_alex]

ok. thanks. I will double check the memory to see if any finding.

[rowid_alex]

Hello,

 

I ran memtest for more than 35 hours and got no error a couple of days ago.

 

 

 

Today I re-run the parity check still found 40 errors.

 

Any other clue?

 

BTW, I am thinking if still needed to have parity drive if I always got errors? If now I have a drive got failed, is it possible to recover the data by the parity drive?

 

Best Regards,

Alex

[JorgeB]

16 minutes ago, rowid_alex said:

I ran memtest for more than 35 hours and got no error a couple of days ago.

 

Unfortunately no errors on memtest doesn't necessarily means there's no problem, only the opposite is true.

 

17 minutes ago, rowid_alex said:

If now I have a drive got failed, is it possible to recover the data by the parity drive?

 

You'd still be able to recover but it would probably have some corrupt files.

 

19 minutes ago, rowid_alex said:

Any other clue?

 

You'll need to start ruling things out, if you have more than a Dimm, try with just one at a time, or use a different board if available

 

[rowid_alex]

ok. I think I will stop here. A couple of errors sound still okay for me. As seen the NPT issue has been resolved on Ryzen build, next year maybe try AMD platform. Thanks a lot anyway!