Parity Errors Help

[Bulletoverload]

Hello,

 

I have been dealing with parity errors that won't seem to go away, and now the number appears to be climbing (up to 157 now). I can't seem to get them to to go away. None of my drives seem to be showing any issues and everything is working correctly, but I hate seeing errors. Can someone suggest next steps or where my issues might be? I have attached diagnostics.

 

Potentially helpful info;

I run parity checks monthly and keep write correction on (not sure if his is good practice). Last few parity checks have thrown errors.

My RAM is non-ECC and running at rated overclock of 3200MHZ (maybe I should try no/lower OC?).

Server has been restarted and multiple parity checks with write correction, errors always remain (though not always the same number of errors)

Current uptime of this diag. is almost 25 days so it should be enough info.

 

Please let me know if there are any questions that would shed extra light. Appreciate any help!

server-diagnostics-20220301-1627.zip

[JonathanM]

Servers and overclock don't mix.

[Bulletoverload]

Just now, JonathanM said:

Servers and overclock don't mix.

Ya I was thinking that but its just XMP. Is it even technically overclocking if the RAM is rated for that speed? But ya, I mentioned that b/c somewhere in the back of my head I've heard complaints of RAM OC and unraid

[JonathanM]

1 hour ago, Bulletoverload said:

Is it even technically overclocking if the RAM is rated for that speed?

Yes. The RAM isn't the limiting factor, it's the CPU / chipset. Most RAM is rated for way higher speeds than the CPU can stably drive.

[Bulletoverload]

16 minutes ago, JonathanM said:

Yes. The RAM isn't the limiting factor, it's the CPU / chipset. Most RAM is rated for way higher speeds than the CPU can stably drive.

And you would expect that to be causing the parity errors? 

 

My CPU and Motherboard officially support 3200mhz ram, which is what I'm running at, so I'm surprised there would be issues. 

Edited March 1, 2022 by Bulletoverload

[JonathanM]

31 minutes ago, Bulletoverload said:

My CPU and Motherboard officially support 3200mhz ram, which is what I'm running at, so I'm surprised there would be issues. 

According to your diagnostics, the maximum supported speed with the current configuration is 2133.

[Bulletoverload]

I have 2 slots filled with single rank, so I think my max is 2933, which is still lower than what I have set, so this must be my issue then I assume. 

[ChatNoir]

6 hours ago, Bulletoverload said:

I have 2 slots filled with single rank, so I think my max is 2933, which is still lower than what I have set, so this must be my issue then I assume. 

Your diagnostics disagree.

It says dual rank, 2 of 4 bank used, so 2400.

[ChatNoir]

9 hours ago, Bulletoverload said:

I run parity checks monthly and keep write correction on (not sure if his is good practice).

As a side note, it is NOT recommended.

Say one of your data drive is actually acting up. Writing the correction to parity will write the wrong information to your parity drive(s).

 

It is better to assess the situation, then decide what to do. Trust parity or write the correction.

[Bulletoverload]

6 hours ago, ChatNoir said:

Your diagnostics disagree.

It says dual rank, 2 of 4 bank used, so 2400.

2400 it is then. Much appreciated thanks very much! 

[Bulletoverload]

6 hours ago, ChatNoir said:

As a side note, it is NOT recommended.

Say one of your data drive is actually acting up. Writing the correction to parity will write the wrong information to your parity drive(s).

 

It is better to assess the situation, then decide what to do. Trust parity or write the correction.

I appreciate this. Will change this setting. Thanks!