nicecube Posted September 13, 2023 Share Posted September 13, 2023 (edited) Before stopping the array i stopped all dockers and Vm's My parity is valid and i have to replace a disk i dont want to hard shutdown I have the following error spamming in my logs Sep 13 10:44:12 Tower emhttpd: shcmd (17757): umount /mnt/disk17 Sep 13 10:44:12 Tower root: umount: /mnt/disk17: target is busy. Sep 13 10:44:12 Tower emhttpd: shcmd (17757): exit status: 32 Sep 13 10:44:12 Tower emhttpd: Retry unmounting disk share(s)... tower-diagnostics-20230913-1045.zip Edited September 13, 2023 by nicecube Quote Link to comment
JorgeB Posted September 13, 2023 Share Posted September 13, 2023 Terminal window/SSH session opened on that disk? Something is still using it. Quote Link to comment
nicecube Posted September 13, 2023 Author Share Posted September 13, 2023 22 minutes ago, JorgeB said: Terminal window/SSH session opened on that disk? Something is still using it. No, there is no connection. I am the only one using the server. The last time I tried to shut down the array, I had the same problem with the same disk. I have tried to check if something is using the disk but this command return nothing lsof | grep /mnt/disk17 Quote Link to comment
Solution nicecube Posted September 13, 2023 Author Solution Share Posted September 13, 2023 I found the solution on the forum umount /var/lib/docker Quote Link to comment
itimpi Posted September 13, 2023 Share Posted September 13, 2023 The fact it was keeping disk17 from unmounting suggests that the docker.img file was on disk17? Ideally you want this on a pool for better performance. Note also that that particular problem was fixed in the 6.12.3 release so you may want to update your system. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.