Repeat parity errors for same sectors

[Leondre]

I seem to be getting repeat parity errors for the same sectors. Smart status on all the drives looks fine. Does anyone know what I should do to figure out what the issue is and fix it?

 

Jul 29 19:05:46 Tower kernel: md: correcting parity, sector=3519069768

Jul 29 19:05:46 Tower kernel: md: correcting parity, sector=3519069800

tower-diagnostics-20160729-2034.zip

[BRiT]

Run SMART short tests on the array drives to begin with.

[Leondre]

Ran the short test on all drives, all returned 'Completed without error'.

[testdasi]

Run long test then. You can run all in parallel.

[JorgeB]

You can also try this:

 

http://lime-technology.com/wiki/index.php/FAQ#How_To_Troubleshoot_Recurring_Parity_Errors

[trurl]

Also you might find this old thread interesting. Don't think this has been reported recently but not sure if it was ever resolved.

 

parity errors, possibly the same ones recurring from test to test

[Leondre]

Run long test then. You can run all in parallel.

 

The extended SMART test completed without error on all drives.

 

You can also try this: http://lime-technology.com/wiki/index.php/FAQ#How_To_Troubleshoot_Recurring_Parity_Errors

 

I attempted that but was unable to get the script to run. I'm not all that experienced in all this stuff so I probably screwed it up somehow. Getting "./md5_sdd.sh: /bin/bash^M: bad interpreter: No such file or directory"

 

Also you might find this old thread interesting. Don't think this has been reported recently but not sure if it was ever resolved.

 

https://lime-technology.com/forum/index.php?topic=38359.msg373934#msg373934

 

I actually did read through that thread before making this. It doesn't seem like it was ever resolved.

 

I also came across this older thread in my research, appears to be the same issue - https://lime-technology.com/forum/index.php?topic=44248

 

It looks like they are assuming the issue is with the AOC-SAS2LP-MV8, which I have. Like the above threads, it seems that the parity issues return if the disks spin down or if the machine is power cycled. Once a correcting parity check has been run I will not get errors again until one of those conditions is met. So at this point I guess I just need to replace that card.