[SOLVED]"Parity is Invalid" but array performed parity check with 0 errors

[Douglas_D]

Hey everyone, I'm running on 6.2.0-rc2 and last week I noticed my dashboard said that my Parity is invalid.  I looked through my log, but unfortunately I have 2 security cameras hitting my server via FTP, so it has blown out the logs of whenever this happened or whatever caused it.  Since then though, my monthly parity check went through and came back with 0 errors.  I'm not quite sure what to do next.  I haven't rebooted my server yet just in case I should do something else before that.  I don't see any drives with SMART errors, everything has a green thumbs up. Additionally, I never received any emails saying that parity failed, but I do get other email notifications, so I know that is still functioning.

 

I've attached my diagnostics zip if anyone wouldn't mind pointing me in the right direction.

 

Secondary question: Is there a way to disable log entries for my cameras hitting the FTP and also, anyone have any idea what these message are about?

 

Aug  6 04:41:01 Galaxy root: sh: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php: No such file or directory

Aug  6 04:41:01 Galaxy root: sh: /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php: No such file or directory

 

Full Diagnostics Log:https://1drv.ms/u/s!Ai6lkoezA2pIgcZF4LC6RdYe4NwbNA

(I couldn't attach the log to the post as it's 1MB)

 

Setup:

unRAID 6.2.0 rc2

4x 4TB WD40EFRX storage drives

1x 4TB WD40EFRX Parity drive

1x INTEL 180GB SSD Cache drive

1x 8GB ADATA USB flash drive

1x 1TB WD1001FALS unassigned drive

[BobPhoenix]

Don't have anything to tell you except to report your link is for your diagnostics based on the file name.  Posted this so that someone that can interpret them knows it isn't just your syslog at your link.

[JorgeB]

You probably have a GUI error, not disk, update to rc3 and reboot, if it doesn't fix it post a dashboard screenshot.

[Douglas_D]

Thank you guys for your feedback, it appears it was a GUI glitch.  I upgraded to rc3 and restarted and now parity is valid again