Drives Not Entering Standby (Spindown) as Configured in OpenMediaVault 7.5.0

Describe the bug

I am experiencing an issue where my drives (sda and sdb) do not go into standby mode, even though I have configured the settings in the OpenMediaVault web UI to have them go into standby after 30 minutes of inactivity. I’ve disabled APM since my drives (sda and sdb - WD Red WD40EFPX-68C6CN0) do not support APM features. However, when I manually run the command smartctl --set=standby,now /dev/sda and smartctl --set=standby,now /dev/sdb in the console, both drives go into standby mode as expected and remain in this mode.

Additionally, after configuring the Spindown time and APM options in the OpenMediaVault web UI. Here is the content of the scripts generated by OMV for sda and sdb. /etc/smartmontools/hdparm.d/ if [ -b '/dev/disk/by-id/ata-WDC_WD40EFPX-68C6CN0_WD-WX32D94RA2P5' ]; then smartctl --set=standby,241 --set=wcache,off /dev/disk/by-id/ata-WDC_WD40EFPX-68C6CN0_WD-WX32D94RA2P5 fi

To Reproduce

Steps to reproduce the behavior:

Install OpenMediaVault 7.5.0 with the OS on a separate SSD (sdc).
Set up drives sda and sdb as data drives (ZFS mirror, zfs scrub scheduled once a month).
Enable SSH and NFS services only.
Set the standby option for the drives (sda, sdb) to 30 minutes in the OpenMediaVault web UI.
After selecting the spindown time and APM options, check the generated script in /etc/smartmontools/hdparm.d/.
Wait and observe that the drives do not enter standby mode.
Check the system logs (journalctl) for any relevant information.

Expected behavior

I expect that when the standby timeout of 30 minutes is reached, the drives (sda and sdb) will automatically go into standby mode as configured in the OpenMediaVault web UI. However, the drives remain active until I manually issue the standby command via smartctl.