chrisb42

I have no VMs and only one app in Docker, but unloading that also doesn't solve the problem, the disks just spin right back up after about a minute. Not sure what else I can look at, especially since everything has been fine for years before this started happening.

Anyone have any suggestions what could cause my drives to spin up again?

Sadly, it seems the plugin doesn't have any information what causes the SMART reads or spinups, nothing is being shown. Attached the diagnostics; thanks! zaphod-diagnostics-20250211-1722.zip

Thanks, just installed the file activity plugin - will see if I can find out more with that.

Hi all, Running the latest version of the 6 branch (6.12.15), but this problem has started some time last year I think. I've been using this server for a long time, and the drives always used to spin down when not in use after two hours, which I believe is the default setting. But at some point they no longer did spin down, or at least they no longer stay spun down. Looking at the logs, it seems the system reads the SMART info shortly after I spin them down manually, which mean within a minute or so they are back up. At least that's what it looks like to me: Feb 11 16:40:30 Zaphod webGUI: Successful login user root from 192.168.88.18 Feb 11 16:41:57 Zaphod emhttpd: spinning down /dev/sdc Feb 11 16:41:59 Zaphod emhttpd: spinning down /dev/sdb Feb 11 16:42:03 Zaphod emhttpd: read SMART /dev/sdb Feb 11 16:42:10 Zaphod emhttpd: read SMART /dev/sdc Feb 11 16:42:10 Zaphod emhttpd: spinning down /dev/sdg Feb 11 16:42:11 Zaphod emhttpd: spinning down /dev/sdf Feb 11 16:42:11 Zaphod emhttpd: spinning down /dev/sde Feb 11 16:42:13 Zaphod emhttpd: spinning down /dev/sdd Feb 11 16:42:14 Zaphod emhttpd: spinning down /dev/sdh Feb 11 16:42:14 Zaphod emhttpd: spinning down /dev/sdj Feb 11 16:42:16 Zaphod emhttpd: spinning down /dev/sdi Feb 11 16:42:38 Zaphod emhttpd: spinning down /dev/sdb Feb 11 16:42:43 Zaphod emhttpd: spinning down /dev/sdc Feb 11 16:43:08 Zaphod emhttpd: read SMART /dev/sdf Feb 11 16:43:37 Zaphod emhttpd: read SMART /dev/sdd Feb 11 16:43:37 Zaphod emhttpd: read SMART /dev/sdb Feb 11 16:43:37 Zaphod emhttpd: read SMART /dev/sdi Feb 11 16:43:52 Zaphod emhttpd: read SMART /dev/sdg Feb 11 16:43:52 Zaphod emhttpd: read SMART /dev/sde Feb 11 16:44:01 Zaphod emhttpd: read SMART /dev/sdc Feb 11 16:44:18 Zaphod emhttpd: read SMART /dev/sdj Feb 11 16:44:18 Zaphod emhttpd: read SMART /dev/sdh Any idea what could cause this phenomenon? I don't want my drives to be spinning all day long when I only need them occasionally during the day. Thanks!

I thought this might be the case, but I didn't see this behavior on the 8TB drive I added for conversion of a different drive and yet another 2TB drive used for conversion. Oh well, I'll just ignore. Thanks for the quick reply! -Christian

I want to convert another drive in my server to XFS, but the WD 3TB drive I added and formatted with XFS, immediately shows 3GB used, with no files on there yet. Has anyone seen that and knows where those 3GB come from? I'm stumped… Cheers! -Christian