PirateYarr

I will report back if I find the root cause. I did upgrade to 6.12.3 after creating the post so it will also be interesting to see if that made any impact on this.

Thanks for the info. I will have to keep an eye out and check the logs more to figure this out. You gave me enough info for me to continue with confidence. Thanks again!

Thanks for the reply! That was a good find, I didn't know about that. I did not reboot the server manually at that time and I didn't notice it going offline either, so that's very interesting. So "unclean shutdown" refers to Unraid shutting down, or can the same message come from say a faulty VM that crashes and reboots? Because I have no idea what could be causing that unclean shutdown. What is "emhttpd:"?

Greetings! I am currently on Unraid 6.11.5. I have parity check scheduled to run once a month, but it is running several times per month. Sometimes it runs back to back, sometimes with a week or so in between. I am using a continuous parity check, not the mode where it splits it out to several days. I have been wondering if there's is a way to find out what triggers the parity check. So far, the only thing I have found is a strange correlation between the UniFi integration in Home Assistant (HA running as VM in Unraid) and the parity checks. When the HA integration accesses my Unifi Controller (which runs in a Docker container in Unraid), many of the parity checks start at the same minute as that access is made, but not every time. I find this very strange. Does anyone have any advice on where to start looking to find the reason that I get more parity checks than I ask for? Thanks! Edit: I should add that I have not always had this problem. I am pretty sure it came after I started installing more things on my Unraid server, such as home assistant. husky-diagnostics-20230717-0959.zip