July 28, 20232 yr Hi All I had to cut the power yesterday, and now again I cant stop my server keep getting the: Jul 28 18:53:57 PLEXZONE emhttpd: shcmd (71069): umount /mnt/cache_appdata Jul 28 18:53:57 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:53:57 PLEXZONE emhttpd: shcmd (71069): exit status: 32 Jul 28 18:53:57 PLEXZONE emhttpd: Retry unmounting disk share(s)... Jul 28 18:54:02 PLEXZONE emhttpd: Unmounting disks... Jul 28 18:54:02 PLEXZONE emhttpd: shcmd (71070): umount /mnt/cache_appdata Jul 28 18:54:02 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:54:02 PLEXZONE emhttpd: shcmd (71070): exit status: 32 Jul 28 18:54:02 PLEXZONE emhttpd: Retry unmounting disk share(s)... Jul 28 18:54:07 PLEXZONE emhttpd: Unmounting disks... Jul 28 18:54:07 PLEXZONE emhttpd: shcmd (71071): umount /mnt/cache_appdata Jul 28 18:54:07 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:54:07 PLEXZONE emhttpd: shcmd (71071): exit status: 32 Jul 28 18:54:07 PLEXZONE emhttpd: Retry unmounting disk share(s)... Jul 28 18:54:12 PLEXZONE emhttpd: Unmounting disks... Jul 28 18:54:12 PLEXZONE emhttpd: shcmd (71072): umount /mnt/cache_appdata Jul 28 18:54:12 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:54:12 PLEXZONE emhttpd: shcmd (71072): exit status: 32 Jul 28 18:54:12 PLEXZONE emhttpd: Retry unmounting disk share(s)... Jul 28 18:54:17 PLEXZONE emhttpd: Unmounting disks... Jul 28 18:54:17 PLEXZONE emhttpd: shcmd (71073): umount /mnt/cache_appdata Jul 28 18:54:17 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:54:17 PLEXZONE emhttpd: shcmd (71073): exit status: 32 Jul 28 18:54:17 PLEXZONE emhttpd: Retry unmounting disk share(s)... I did a Diagnostic file attached below, hope some one can help me? VM and dockers are stopped! I finally got it stopped using: umount -l /dev/loop2 But I would like to know the cause of this 🙂 plexzone-diagnostics-20230728-1855.zip
July 28, 20232 yr Community Expert Solution There is a known problem with docker that can cause this that had been fixed in the 6.12.3 release.
July 28, 20232 yr Author THANKS! @itimpi I think that I got e-mails bedfore when there was a new build released from Unraid? Anyway thanks for the heads-up! I will update it right away! As my header in this post says I also thought it was related to the latest Unraid build, never seen this before 🙂
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.