When running parity checks the system is unable to fix parity checks despite the option being selected when the parity check is run.  For example the last three completed parity checks had the following results, 1000 errors, 866 errors, and 2345.

 

Since starting with unRAID I've had some hardware issues which caused several unclean shutdowns, dying motherboard, replaced with new AMD setup, which then had C state issues.  Everything is now stable with the exception of this parity issue.

 

So the current setup is version 6.6.6, Ryzen 1600X (not overclocked), 16 gb Vengeance LPX DDR4 3000 Mhz C15, Asus Prime B350 Plus, GTX 750ti.

 

Drives initially Parity x 2, Toshiba X300 5 TB, Data 4 TB WD Red, 2 x 3 TB WD Green, 3 x 1 TB Hitachis, Cache 128 GB Crucial M4

 

Due to the parity problems I decided to simply things and removed a parity drive and the three Hitachis as the parity drive flagged up a fault on an extended smart test which I'm not familiar with, and two of the Hitachis had minor issues.

 

I've attached the system log and the three SMART reports.

 

Any help gratefully received

 

syslog.txt

TOSHIBA_HDWE150_Z5GAK7DWF57D-20190204-1851.txt

Hitachi_HDS721010CLA332_JP2940HD0LED4C-20190204-1851.txt

Hitachi_HDS721010CLA332_JP9930HZ0M5Y9H-20190204-1853.txt

The problem is that you're getting different errors, you likely have a RAM problem, Ryzen with overclocked RAM is known to cause sync errors, respect the max RAM speeds:

 

 

Then run another couple of checks, it's normal for the 1st one to still find errors.

Will do.

 

Just got so used to using XMP memory profiles in recent years, I stopped thinking of it as being overclocked.   Running parity check now.

 

Thanks for the help.

1 hour ago, Paul4G63 said:

I've attached the system log and the three SMART reports.

In future, it is much easier for you and for us if you just go to Tools - Diagnostics and attach the complete diagnostics zip file. It has all of those things you attached separately as well as other things that will help give a more complete picture of your situation.

With regards to the diagnostics zip file, wiIl use this in future, been a long day and by reading to the end of the read me first, I stupidly got blinkered by all the subsequent references to the syslog file, so mistakenly posted that, rather than using the diagnostics tool mentioned in the second paragraph referring to the version I'm actually using.