I have spin down time set to 3 hours, and did everything I could to mitigate anything spinning up disks such as turning off scanning for Fix Common Problems, but my array turns on every time my personal computer turns on, after logging in. It doesn't seem to to matter if I have shares on Unraid mapped or not. It's also a fresh windows install so I have nothing that should be connected to anything on Unraid during boot.

 

I do run homepage (gethomepage.dev), which I thought might be the culprit, but when I spin down my drives, and restart my computer, it doesn't wake the array (only the first boot of the day, or maybe after a long time?).

 

I'm also already using File Activity to see if any files are being read/modified, but there's nothing in there since 3AM for mover operations. If it matters, nextcloud used to spin up the array during computer boots because it was reading a certificate file, but I mapped the path to a cache share, so it no longer appears in file activity.

 

It doesn't seem to be anything accessing files given there's nothing in file activity and both parity drives spin up along with disk1, vs only disk1 spinning up if a file is being read.

 

Does anyone have any other ideas what might be waking my array? The only thing in my syslog after move entries is
Jul  6 09:17:23 UNRAID emhttpd: read SMART /dev/sdd <--Disk1
Jul  6 09:19:28 UNRAID emhttpd: read SMART /dev/sdh<--Parity1
Jul  6 09:19:28 UNRAID emhttpd: read SMART /dev/sdi<--Parity2

Edited July 7, 20233 yr by jinra
adding more information

Are there any mapped drives to Unraid in your PC?

I had shares mapped, but even after a fresh windows install with no shares mapped it was still happening.