Disk spindown not working - disk is accessed by pool-udisksd

Hi,

I tried troubleshooting this issue from posts I found on this forum and others too, and with the help of ChatGPT, but nothing helped.

I have a 4TB WD drive that I use for data which I don't access a lot. I also have a 1TB WD drive that is constantly running for Plex, torrents, etc. As I don't use the 4TB one, I always had it configured to spin down after 20 minutes. On my previous server (RPi4, OMV 6, USB HDD enclosures) it worked, but I have another server now (J4125B, OMV 7, SATA connections), and it doesn't work.

After some investigation with btrace I can see that nothing accesses the drive when I don't use it, except pool-udisksd and udisksd.

I tried to apply the OMV settings again (see attached picture), but didn't work. With hdparm -C it is always active/idle. I tried editing /etc/udisks2/udisks2.conf, my config is this now:

[udisks2]
# Comma separated list of modules to load.
# Use asterisk to load all the modules.
modules=*
# Valid options are 'ondemand' or 'onstartup'.
modules_load_preference=ondemand
[defaults]
# Valid options are 'luks1' or 'luks2'
encryption=luks1
[Device wd40]
#PollingInterval=86400
EnableSmart=false

And you can see, I also tried to set the polling rate to a day. (I restarted udisks after modifications)

I tried editing /etc/smartd.conf, but there is a message that it is OMV generated and changes will be lost.

I need SMART monitoring, for my SSD system drive and 1TB HDD I don't care if they are checked every 5 minutes or so by udisks, but my 4TB drive should be checked less frequently, maybe once a day.

I really hope someone can help me with this.
Thanks in advance for the answers,
Matt

Anyone, any idea?

I compared the installed packages dpkg --get-selections | grep -v deinstall output with the output of apt-cache depends udisks2 and apt-cache rdepends udisks2, here is the output:

dbus
fwupd
gnome-disk-utility
gvfs-daemons      
parted
udev

I have a lot of gnome stuff installed, and I don't know why. I will investigate that, and also which packages need the other stuff.

Also, the result of sudo apt-get remove --simulate udisks2:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  exfatprogs gir1.2-evince-3.0 gir1.2-gmenu-3.0 gir1.2-gtksource-4 gvfs-common gvfs-libs libblockdev-crypto2
  libblockdev-fs2 libblockdev-loop2 libblockdev-part-err2 libblockdev-part2 libblockdev-swap2 libblockdev-utils2
  libblockdev2 libcdio-cdda2 libcdio-paranoia2 libgnome-menu-3-0 libgtksourceview-4-0 libgtksourceview-4-common
  libparted-fs-resize0 libportal-gtk4-1 libvolume-key1 nautilus-data
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  gnome-disk-utility gnome-shell-extensions gnome-sushi gvfs gvfs-backends gvfs-daemons gvfs-fuse nautilus udisks2
0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded.
Remv gnome-disk-utility [43.0-1]
Remv gnome-shell-extensions [43.1-1]
Remv gnome-sushi [43.0-2]
Remv gvfs-backends [1.50.3-1]
Remv nautilus [43.2-1]
Remv gvfs [1.50.3-1] [gvfs-fuse:amd64 ]
Remv gvfs-daemons [1.50.3-1] [gvfs-fuse:amd64 ]
Remv gvfs-fuse [1.50.3-1]
Remv udisks2 [2.9.4-4]

So I'm a little confused: how can it be that dbus and udev depends on udisks2 but removing it apparently doesn't break those?

After reading some online sources, I masked udisks2. Will write if the disk spindown error is fixed or if I encounter other problems caused by the masking.

So far so good. The disk is standby. I don't have other issues for now.