jinra

It updates as expected, I usually have to update my docker containers manually by clicking "update all" from the docker page because of this.

I'm wondering if I have something setup incorrectly. I seem to have a similar issue to @ANIMATEK These are my settings, and while my dockers "created" time does change to 6am every morning, it doesn't seem to actually update my containers and I still have "apply update" on most of my apps. It's been this way for quite a while, probably ever since I installed the tool months ago.

Anyone seeing sync issues with Android? I just noticed my Asus Zenfone 9 hasn't synced successfully since 9/26, and the brand new Pixel 8 Pro is seeing the same issue. Syncing still works fine on my PC, mac, and browser extensions, but fail on both Android phones. I can sign into my account just fine, it just seems to be syncing that's broken. My Vaultwarden is running with reverse proxy with HSTS/HTTPS enabled.

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

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