Parity Check Errors Help

[Doug]

Hello,

 

I have been dealing with some Parity Check Errors lately and I cannot seem to get them to clear.  I have ran extended SMART tests on each drive and they each passed.  I am receiving less than 10 errors now but they are never really consistent.  How can I go about pin pointing what is causing this?

 

Here are the details:

 

Unraid 6.1.4

Attached Smart Tests for Each Disk

 

Any advice would be great!

 

Thanks

SMART_Tests.zip

[methanoid]

Not that I know the solution but the general suggestion is to post details of your full machine spec etc...  could be hardware (PSU, drives), could be s/w (old unRAID etc)...

[Doug]

Thanks.  I added the information requested into my signature.

[trurl]

Tools - Diagnostics.

 

Have you done a memtest?

[Doug]

I think this is my issue but i don't know what it means exactly.

[trurl]

Let me know if you don't understand what I asked for and I will elaborate.

Tools - Diagnostics.

 

Have you done a memtest?

[Doug]

Let me know if you don't understand what I asked for and I will elaborate.

Tools - Diagnostics.

 

Have you done a memtest?

 

No I understand.  Finding time to access the server physically is tough.  I have been doing this all remotely!  When I get a chance, I will do a memtest.  I do not have a monitor or anything setup that's easily accessible.  At the moment, I disabled the HDD that I believe is the "ata7.00".  Did a parity sync and am now running a parity check.  Unfortunately that takes 6.5 hours so troubleshooting is limited to twice a day when I am doing these things.

 

I will keep you updated on if what I just did corrects the issue which will tell me it's the drive I disabled or not.  If not, then I will run a memtest.

 

Thanks for your response!

[Doug]

Well I have an update after running another parity check all morning. After disabling the drive that corresponded to ata7.00 I received no errors on the parity check. So that tells me it can be one of three things. The drive itself,sata cable, or sata port! 

 

I think the next step is to swap it with a working drive (possibly smaller) to make the parity check go a little faster to determine if I still receive errors. If I do then it's the cable or port. If I don't then I would have to assume it's the drive.