I had my spin down set to 2 hours and it worked nicely for a while. I needed to change both my parity and disk1 HDD in the system and also moved the machine to another case. After the parity rebuild and disk1 data rebuild on the new drives, I noticed that I cannot keep my disks spun down. They always spin up after a few seconds/minutes. I don't know if the issue was present before the HDD changes sadly. File activity plugin does not show any file access, it happens with VMs stopped and Docker disabled also. I installed Dynamix Cache Directories plugin too. I cannot find what is causing it.
Can someone point me in a direction with troubleshooting this?

naspolya-diagnostics-20250623-1624.zip

Edited June 23, 20251 yr by Lecso

If you haven't yet rebooted after the rebuild, try that, it can sometimes help.

4 minutes ago, JorgeB said:

If you haven't yet rebooted after the rebuild, try that, it can sometimes help.

I already did. What I noticed however, if I completely disabled VM manager, my disks did not spin up in minutes. Enabling it started my Home Assistant VM, which accessed its backups on startup, it was logged in file activity plugin. I then let the HA VM run, and spun my disks down. They were spun up in a minute, but no file access in the plugin for this spin up. So it is probably my HA VM, but how do I find out what it does?

Let me attach my syslog again, with the VM manager start and then you can see the manual spin down and then spin up in a minute.

syslog.txt

That suggests something related to the VM is using the array.

I might have found the culprit:
I had this ha-unraid-connect custom integration on Home Assistant, which is still in beta, together with the GraphQL API. After I removed the integration, I could spin down my disks and they are spun down for 15 minutes as of now.