when i try to shut down or reboot the process hangs and i get the log spammed stating that it can't unmount mnt/cache. all my containers stop but then it just keeps repeating the attached error message. after about 20 or so minutes it will finally continue. but it is alway dirty and wants to parity check the next time it starts up. any help figuring out what this is and how to correct? i am on 7.3.2.

enterprise-d-diagnostics-20260823-1918.zip

Edited August 25Aug 25 by knights_of_pine

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.

Common causes are:

1. You left a terminal window open browsing the disk (you typed in cd /mnt/cache and forgot to exit)

2. SMB access, you were browsing an exported share on windows explorer and it has a file open/in use that happened to be on the cache pool.

you can try and run lsof /mnt/cache to see if it reports any files in use next time this happens and if shows something it should also show a process which you can work backwards from to see what ran that process.

On 8/24/2026 at 11:38 PM, JorgeB said:

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.

I will try this weekend the steps above to try to narrow it down.

13 hours ago, MowMdown said:

Common causes are:

1. You left a terminal window open browsing the disk (you typed in cd /mnt/cache and forgot to exit)

2. SMB access, you were browsing an exported share on windows explorer and it has a file open/in use that happened to be on the cache pool.

you can try and run lsof /mnt/cache to see if it reports any files in use next time this happens and if shows something it should also show a process which you can work backwards from to see what ran that process.

I have two user scripts that are running, could this be the cause?

39 minutes ago, knights_of_pine said:

I will try this weekend the steps above to try to narrow it down.

I have two user scripts that are running, could this be the cause?

potentially, depends on what they are doing.