SnapRAID: Parity drive not spinning down since last sync job

I've noticed that the last remaining HDD in my all SSD system is suddenly no longer going into into standby like it used to do. The disk is only used as a parity drive for snapRAID and, besides a weekly short SMART self-test, no other process is accessing the share for this drive.

As far as I can tell, the disk has kept spinning since the last automated snapRAID. According to the log, the job was done ofter seven minutes. The configuration of the drive hasn't changed and is still set to spindown.

Log SnapRAID Job.txt

Can I check somewhere what is keeping the disk from properly going into standby again?

I had to restart the whole system to get the drive to spin-down again. But this is obviously not the right solution. I'll monitor the situation and see if it's going to happen again when the next scheduled snapRADI sync job is run.

As I've already rebooted the system, I'm unable to check that. But I'll give that a try if and when the problem occurs again.

Quote from ryecoaaron

Can't really help much since I don't spin down drives and most of my OMV is on nvme or virtual disk. But I am curious if the Spin down button on the Drives tab of the Snapraid plugin would spin the drive down?

So, the weekly scheduled task was run last night and the parity HDD again has kept running. The drive immediately goes into standby again, when I manually use the "spin down" option unter SnapRAID > Arrays.

The task is running the following command:

for conf in /etc/snapraid/omv-snapraid-*.conf; do /usr/sbin/omv-snapraid-diff ${conf}; done

Just noticed that the drive is spinning again. But this time I can't manually spin down the disk again.

Quote

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; /usr/bin/snapraid --filter-disk Parity_(HDD1) down 2>&1':

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; /usr/bin/snapraid --filter-disk Parity_(HDD1) down 2>&1': in /usr/share/openmediavault/engined/rpc/snapraid.inc:547

Stack trace:

#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(628): OMVRpcServiceSnapRaid->{closure}()

#1 /usr/share/openmediavault/engined/rpc/snapraid.inc(521): OMV\Rpc\ServiceAbstract->execBgProc()

#2 [internal function]: OMVRpcServiceSnapRaid->executeDriveCommand()

#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()

#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()

#5 /usr/sbin/omv-engined(546): OMV\Rpc\Rpc::call()

#6 {main}

Display More

Another interesting observation:

When the HDD is spinning from last nights SnaipRaid job, simply login into the OMV gui seems to reset the HDD spindown timer and the HDD goes into standby after the 5 minutes set as the spindown timer value.

I actually already have enabled the spin-down-timer for the parity drive. And this works fine during everyday use. Only the SnapRaid job somehow refuses to let the drive spin down again.