[SOLVED] Parity Check Reported 7 Errors

[snuffy47]

Hello

 

Version - Version: 6.8.3

Parity Check/fix once a month

 

I have had some problems with Disk 1 in past and some other oddities\

 

Looking for some help finding the actual errors and understanding if they are telling me anything

 

I do have system logging on also if needed

 

Attached is system log during and after parity check

 

Unraid Parity check: 01-05-2020 00:01
Notice [TOWER] - Parity check started
Size: 8 TB

Unraid Parity check: 02-05-2020 06:35
Notice [TOWER] - Parity check finished (7 errors)
Duration: 1 day, 6 hours, 34 minutes, 22 seconds. Average speed: 72.7 MB/s

syslog.rtf

Edited May 6, 2020 by snuffy47

[Frank1940]

The Gurus will need your Diagnostics file.    Tools   >>>   Diagnostics    Post it up in a new post!

[snuffy47]

Okie dokie

 

Rerally hope to get some coaching on what to be looking for too

 

 

tower-diagnostics-20200503-2242.zip

[JorgeB]

Any unclean shutdown since last check? In any case you should run another one and if there are sync errors again post new diags.

[snuffy47]

No unclean shutdowns for a month

 

Did you see sync errors in system log?

 

Will run another check

[JorgeB]

10 minutes ago, snuffy47 said:

Did you see sync errors in system log?

Yes

[snuffy47]

Okay the second parity chaeck reported back clean

 

I have also stopped the auto correction for my scheduled parity checks for now

 

Johnnie when these happen what do I search for in log to find them?

 

Thanks

[JorgeB]

May  1 10:32:59 Tower kernel: md: recovery thread: P corrected, sector=2012443264
May  1 10:32:59 Tower kernel: md: recovery thread: P corrected, sector=2012443272
May  1 10:32:59 Tower kernel: md: recovery thread: P corrected, sector=2012443280
May  1 10:32:59 Tower kernel: md: recovery thread: P corrected, sector=2012443288
May  1 10:32:59 Tower kernel: md: recovery thread: P corrected, sector=2012443296
May  1 14:28:33 Tower kernel: md: recovery thread: P corrected, sector=2965791232
May  1 14:28:33 Tower kernel: md: recovery thread: P corrected, sector=2965791240

P.S.: On a non correcting check it will be logged as "incorrect" instead of "corrected".

[snuffy47]

Howdy

 

Appreciate the help and found these in the log 

 

Is there specifics that these are telling me or is there anything else I can do to isolate what may have caused them?

 

[JorgeB]

If it doesn't happen again it was most likely an unclean shutdown, if there are more in the future there's a likely a hardware problem somewhere.

[snuffy47]

Thanks again