6 minutes ago, MarkRMonaco said:

RAM clock back down to the base/stock XMP setting (3000MHz)

This is still above the max officially supported RAM speed for your CPU.

48 minutes ago, JorgeB said:

This is still above the max officially supported RAM speed for your CPU.

I get that and will drop it down further, if necessary. - However, I just changed several things at once (again), and need to see if any of it has made an impact.

Edited September 16, 20205 yr by MarkRMonaco

Ok, I just received a CRC error on a completely different drive. Therefore, I'm pretty confident that the cable itself is bad (or going bad). - Since that particular drive was my only parity drive. I'm going to pause the rebuild just to be safe. I'm going to shut down the server and have already placed a store pickup order for replacement cables (going to replace all 4 since the original cables were a sleeved bundle) from my local Fry's. -- Just waiting on the "order ready" confirmation...

Edited September 16, 20205 yr by MarkRMonaco

Just another update... I picked up the replacement SATA-III cables and installed them. Of course, that means that I now need to wait for the drive to rebuild again since it was postponed earlier today.

 

If anyone has any further insight into the Syslog issue, I would love to get that up and running.  Thanks in advance.

Everything appears to be fixed on my end and no further CRC errors have shown up since the cables were replaced. - For the time being, I keep the RAM at the factory XMP speed without any additional overclocks applied.

 

As for the Syslog server, it is still not functioning correctly. Therefore, I may look into either a Docker that can serve the same purpose (making the Unraid server itself just a client to send logs) or one of my Raspberry Pi's.

Edited September 18, 20205 yr by MarkRMonaco