Hello !
I'm here today because I have an issue with something in my OMV installation. My two HDD wake up and spin-up for no reason periodically.
I have installed OMV many years ago, gone through many updates and the issue remains since as far as I remember at least 4 years 
The current versions are :
ii openmediavault 7.7.20-1 all openmediavault - The open network attached storage solution
ii openmediavault-flashmemory 6.2 all folder2ram plugin for openmediavault
ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive
ii openmediavault-omvextrasorg 6.3.6 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-resetperms 6.0.3 all Reset Permissions
ii openmediavault-wetty 7.0.1-1
uname -a
Linux openmediavault 6.12.43+deb12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.43-1~bpo12+1 (2025-09-06) x86_64 GNU/Linux
Through the years I tried many things that I forgot, with the help of google and some existing topics in this forum.
I have disabled smart monitoring.
Lastly I put GPT to work. With his help I could eliminate possibilities.
It gives me this script to figure out which process could be faulty :
PATH=/usr/sbin:/usr/bin:/sbin:/bin
LOGFILE="/var/log/disk_wakeup.log"
DISKS=(/dev/sdb /dev/sdc)
STATE_DIR="/tmp/disk_states"
mkdir -p "$STATE_DIR"
log() {
echo "$(date '+%F %T') - $1" >> "$LOGFILE"
}
for DISK in "${DISKS[@]}"; do
NAME=$(basename "$DISK")
STATE_FILE="$STATE_DIR/$NAME.state"
CURRENT_STATE=$(hdparm -C "$DISK" 2>/dev/null | awk '/state/ {print $4}')
[ -z "$CURRENT_STATE" ] && continue
if [ -f "$STATE_FILE" ]; then
PREV_STATE=$(cat "$STATE_FILE")
else
PREV_STATE="$CURRENT_STATE"
fi
if [ "$PREV_STATE" = "standby" ] && [ "$CURRENT_STATE" != "standby" ]; then
log "$NAME woke up (was $PREV_STATE → now $CURRENT_STATE)"
log "Recent activity on $NAME (last 5 seconds):"
grep "$NAME" /proc/diskstats >> "$LOGFILE" 2>/dev/null
lsof +D /mnt 2>/dev/null | grep "$NAME" >> "$LOGFILE"
ps -eo pid,comm,etime,cmd | head -n 15 >> "$LOGFILE"
log "----"
fi
echo "$CURRENT_STATE" > "$STATE_FILE"
doneWhich gives me that output in a log file :
2025-11-09 20:59:10 - sdc woke up (was standby → now active/idle)
2025-11-09 20:59:10 - Recent activity on sdc (last 5 seconds):
8 32 sdc 5617 4826 102284 144462 43 55 690 4692 0 26076 150137 0 0 0 0 18 982
8 33 sdc1 5522 4826 98844 144174 43 55 690 4692 0 27072 148866 0 0 0 0 0 0
PID COMMAND ELAPSED CMD
1 systemd 03:02:45 /sbin/init
2 kthreadd 03:02:45 [kthreadd]
3 pool_workqueue_ 03:02:45 [pool_workqueue_release]
4 kworker/R-kvfre 03:02:45 [kworker/R-kvfree_rcu_reclaim]
5 kworker/R-rcu_g 03:02:45 [kworker/R-rcu_gp]
6 kworker/R-sync_ 03:02:45 [kworker/R-sync_wq]
7 kworker/R-slub_ 03:02:45 [kworker/R-slub_flushwq]
8 kworker/R-netns 03:02:45 [kworker/R-netns]
12 kworker/u16:0-i 03:02:45 [kworker/u16:0-ipv6_addrconf]
13 kworker/R-mm_pe 03:02:45 [kworker/R-mm_percpu_wq]
14 rcu_tasks_kthre 03:02:45 [rcu_tasks_kthread]
15 rcu_tasks_rude_ 03:02:45 [rcu_tasks_rude_kthread]
16 rcu_tasks_trace 03:02:45 [rcu_tasks_trace_kthread]
17 ksoftirqd/0 03:02:45 [ksoftirqd/0]
2025-11-09 20:59:10 - ----
2025-11-09 20:59:11 - sdb woke up (was standby → now active/idle)
2025-11-09 20:59:11 - Recent activity on sdb (last 5 seconds):
8 16 sdb 5617 3310 90147 119915 17 12 138 404 0 18408 120709 0 0 0 0 10 389
8 17 sdb1 5529 3310 86763 119574 17 12 138 404 0 18520 119979 0 0 0 0 0 0
PID COMMAND ELAPSED CMD
1 systemd 03:02:46 /sbin/init
2 kthreadd 03:02:46 [kthreadd]
3 pool_workqueue_ 03:02:46 [pool_workqueue_release]
4 kworker/R-kvfre 03:02:46 [kworker/R-kvfree_rcu_reclaim]
5 kworker/R-rcu_g 03:02:46 [kworker/R-rcu_gp]
6 kworker/R-sync_ 03:02:46 [kworker/R-sync_wq]
7 kworker/R-slub_ 03:02:46 [kworker/R-slub_flushwq]
8 kworker/R-netns 03:02:46 [kworker/R-netns]
12 kworker/u16:0-i 03:02:46 [kworker/u16:0-ipv6_addrconf]
13 kworker/R-mm_pe 03:02:46 [kworker/R-mm_percpu_wq]
14 rcu_tasks_kthre 03:02:46 [rcu_tasks_kthread]
15 rcu_tasks_rude_ 03:02:46 [rcu_tasks_rude_kthread]
16 rcu_tasks_trace 03:02:46 [rcu_tasks_trace_kthread]
17 ksoftirqd/0 03:02:46 [ksoftirqd/0]
2025-11-09 20:59:11 - ----Conclusion, no user process wakes up my drives.
I finally shutdown some services
sudo systemctl stop nfs-kernel-server smbd docker docker.socket
Then unmount and put drives in standby.
Something auto remount drives and wakes them up.
The last action was to stop these two services than unmount and put drives in standby :
sudo systemctl stop openmediavault-engined
sudo systemctl stop monit
Until then, no more auto remount nor spin up.
I conclude that something was wrong with my OMV.
Am i right ? Does anybody know what happens on my system and how to fix it ?
extra information : Since I reboot the system this morning after I switch every services off ^^, drives have stopped spin-up. I notice this too when I updated omv to 7.7 from 6.x. But after some time it is all happening again.
I wonder if a reboot may temporary solve the issue 
I have not test that yet because it's ok for the moment.
