Disk constantly seeking every 5 seconds after 8.0.6 -> 8.0.7 + md upgrade, no other client activity and all servcies stopped

[edit: omv 8.0.6 was the previous version, not 8.0.4]

I am noticing that my RAID1 drives are seeking every 5 seconds after upgrading from 8.0.6 to 8.0.7. The update also installed openmediavault-md:all 8.0.2-1.

In an attempt to find the culprit, I've also installed iotop to try to find the source, but it doesn't appear to be a user process causing the activity. The only activity I see there is to the NVME boot drive. (command: iotop -bktoqqq -d .5 )

I have also shutdown all services, and 'compose down' on Jellyfin, and stopped the openmediavault-filebrowser 8.0-6 plugin. Rebooted a few times, but symptom still exists.

The update to 8.0.7 seems to have overwritten Disk power management back to defaults. I've changed the two RAID1 drives back to '127' for APM, with a spin down of 20 min. Since the drives are seeking, they're certainly not spinning down.

Further, the RAID1 array /dev/md0 is in a clean state, not resync-ing. Both drives are healthy via SMART.

Additional installed plugins, some from omv-extras:

openmediavault-apt 8.0-4

openmediavault-apttool 8.0

openmediavault-backup 8.0.1

openmediavault-compose 8.1.2

openmediavault-cterm 8.0

openmediavault-filebrowser 8.0-6

openmediavault-ftp 8.0.1-1

openmediavault-md 8.0.2-1

openmediavault-omvextrasorg 8.0.2

openmediavault-podman 8.0-5

openmediavault-remotemount 8.0

openmediavault-sftp 8.0

Jellyfin 10.11.5, via compose plugin

I haven't run software RAID on my other Linux boxes in several years, but I don't remember anything that might cause this.

Anyone else noticing this behavior?

Thanks.

I isolated my problem, it is Jellyfin keeping the disk active.

I thought I had already tested with Jellyfin down, but must have had something else keeping the disk spinning.

Probably a bungled config on my part, or some scheduled Jellyfin task.