Hi!

Every time I reboot my machine, it starts a parity check. If I understand syslog.txt correctly, it's because unmount fails because of a device being busy:

Nov 17 15:35:28 Unraid emhttpd: shcmd (3417785): /usr/sbin/zpool export -f tank
Nov 17 15:35:28 Unraid root: cannot unmount '/mnt/tank/vmdata': pool or dataset is busy

/mnt/tank/vmdata contains data for a vm. The share is mounted in the vm using 9p mode (/etc/fstab):

vmdata /mnt/vmdata 9p trans=virtio,version=9p2000.L,_netdev,rw 0 0 

For a clean shutdown/reboot it's crucial, that all vms shutdown before trying to unmount this share.

My question is, why does this happen? How can I achieve a clean shutdown?

Thx a lot! 🙂

Thorsten

unraid-diagnostics-20251117-1535.zip

Something is keeping that pool busy; you can test by just trying to stot the array. You should get the same error:

Disable Docker and VM service and reboot in safe mode, start the array and see if it stops, if yes, retest again after booting in normal mode to rule out a plugin issue, leave the services still disabled, if still OK enable one of the services and retest, then the other, note that if the issue happens with the docker service enabled only, you may need to try enabling one or a few containers at a time to find the culprit.

27 minutes ago, Tom7320 said:

For a clean shutdown/reboot it's crucial, that all vms shutdown before trying to unmount this share

Make sure that the timeout for VMs (under Settings->VM Manager (advanced view) is sufficient to allow your VMs to shutdown, and that the Shutdown timer for the disks (under Settings->Disk Settings) is larger than the VM value.

Uh. That was quick! Thx a lot!! 🙂

I'll try it out and report my findings! My shutdown time for disks was 90s, the vm shutdown time was 120s. This might have been the problem. But I have to wait until parity check is finished... 😉

Have a nice evening