How can I tell what is causing my parity errors? I had a bunch so this is a screenshot of me running my second parity check. Server has been solid for a cpl years no issues. Will run a memory check once this parity check is complete. I stopped the correcting after this didnt notice it was on.

hal.txt

smartdisk.zip

Check your drive's cabling.

Memory test showed no issues, Waiting on new cables, will clean computer out at that time also.

Cleaned computer out, re-seated cables , replaced parity drive cable still getting errors on check. What are my options for tracking down the faulty drive? Don't understand why the logs are not configured to tell me what drive is reporting different than the parity drive.

syslog.txt

If you did have a cabling problem while it was doing a correcting parity check, then maybe the parity was "corrected" and is now wrong. Are you using locking SATA cables? Maybe a power problem?

 

Try a couple or more non-correcting parity checks and see if it gets the same number of errors each time. If not then you still have a problem.

Was 150 errors last full check now its at 136 errors at 1% checked. If i'm adding files to the array during a parity check will that cause errors? I just ordered 3 4TB drives to swap for some of the 2TB in the array. Should be here Wednesday.

Clearing the config and rebuilding the array with just the onboad sata ports first then will add drives back one at a time.

Don't understand why the logs are not configured to tell me what drive is reporting different than the parity drive.

Single parity doesn't work like that. http://lime-technology.com/wiki/index.php/FAQ#How_does_parity_work.3F

Don't understand why the logs are not configured to tell me what drive is reporting different than the parity drive.

As has been stated parity does not tell you which drive has failed if unRAID can apparently read from all of them, but the values read from the data drives and used to compute parity do not match the value read from the parity drive.  In this case it is known there is an error, but not which drive caused it.  It is only in the case of a particular drive reporting a hard error (so it is known which drive has a problem) can the value computed from the other data drives plus parity drive give you what should be on the sector from the failed drive.

Swapping a  4SATA port pci-e card to replace the 2sata port pci and 2sata port pci-e cards I had installed in my machine as well as changing out those sata cables seems to have resolved my issues.