Version 7.7.2-1 (Sandworm)
Kernel - Linux 6.12.12+bpo-amd64
OMV is running as a VM on Proxmox.
I added an SSD to my homelab and before I did that, I ran apt-get update and apt-get upgrade on the container. I added the SSD, formatted to EXT-4 and after I booted the system up, neither drives respect the spindown times. OMV has control of the SATA controller passed through as a PCI device from Proxmox.
It appears that the spinning disk does not respect the smartctl standby command -
smartctl -s standby,now /dev/disk/by-id/ata-ST16000NM001G-2KK103_ZL2F6F4H
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.12.12+bpo-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
Device placed in STANDBY modeThe device says its in standby but checking it immediately after still shows the device in active/idle state
hdparm -C /dev/disk/by-id/ata-ST16000NM001G-2KK103_ZL2F6F4H
/dev/disk/by-id/ata-ST16000NM001G-2KK103_ZL2F6F4H:
drive state is: active/idleIt seems like something is accessing the drive but `fatrace` hasn't shown anything accessing the drive.
I installed the diskstats plugin and I can see a constant 400 byte/second write to the disk. I can't seem to figure out what it is
Attached the image with the disk i/o stats
Everything worked fine before I performed the update yesterday and added the SSD. I am not sure if one of those two things may be causing the drive to not spin down.
Any troubleshooting steps would be highly appreciated.
Thank you!
