ryan8382 Posted October 19, 2016 Share Posted October 19, 2016 After upgrading to 6.2.1 and swapping out a drive Docker won't start. My docker image is directly on cache. So it wasn't associated with the drive being swapped. This is what shows in the logs. Oct 19 09:23:01 Tower emhttp: shcmd (3242): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 40 |& logger Oct 19 09:23:01 Tower root: /mnt/cache/docker.img is in-use, cannot mount Oct 19 09:23:01 Tower emhttp: err: shcmd: shcmd (3242): exit status: 1 Oct 19 09:24:02 Tower emhttp: shcmd (3259): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 40 |& logger Oct 19 09:24:02 Tower root: /mnt/cache/docker.img is in-use, cannot mount Oct 19 09:24:02 Tower emhttp: err: shcmd: shcmd (3259): exit status: 1 tower-diagnostics-20161019-0914.zip Quote Link to comment
Squid Posted October 19, 2016 Share Posted October 19, 2016 Delete the image and readd your apps Sent from my LG-D852 using Tapatalk Quote Link to comment
ryan8382 Posted October 19, 2016 Author Share Posted October 19, 2016 Already did that. No go error didn't change. Quote Link to comment
Squid Posted October 19, 2016 Share Posted October 19, 2016 Already did that. No go error didn't change. Did you delete the entire docker image or just remove the applications? Sent from my LG-D852 using Tapatalk Quote Link to comment
Squid Posted October 19, 2016 Share Posted October 19, 2016 Just for the heck of it, can you create the image on disk 1 and see if it works. Then recreate it back on the cache drive. Quote Link to comment
ryan8382 Posted October 19, 2016 Author Share Posted October 19, 2016 Same error on Disk1 Oct 19 10:46:28 Tower emhttp: shcmd (4941): /etc/rc.d/rc.docker start |& logger Oct 19 10:46:28 Tower root: starting docker ... Oct 19 10:47:01 Tower emhttp: shcmd (4959): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/disk1/docker.img' /var/lib/docker 40 |& logger Oct 19 10:47:01 Tower root: /mnt/disk1/docker.img is in-use, cannot mount Oct 19 10:47:01 Tower emhttp: err: shcmd: shcmd (4959): exit status: 1 I'm gong to guess my next option is to roll back to previous version? Quote Link to comment
Squid Posted October 19, 2016 Share Posted October 19, 2016 Same error on Disk1 Oct 19 10:46:28 Tower emhttp: shcmd (4941): /etc/rc.d/rc.docker start |& logger Oct 19 10:46:28 Tower root: starting docker ... Oct 19 10:47:01 Tower emhttp: shcmd (4959): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/disk1/docker.img' /var/lib/docker 40 |& logger Oct 19 10:47:01 Tower root: /mnt/disk1/docker.img is in-use, cannot mount Oct 19 10:47:01 Tower emhttp: err: shcmd: shcmd (4959): exit status: 1 I'm gong to guess my next option is to roll back to previous version? I'd say the next step is to disable docker, delete the image, then reboot... Then try it all again.... This isn't making a ton of sense to me either Quote Link to comment
ryan8382 Posted October 19, 2016 Author Share Posted October 19, 2016 Deleted Docker.img and go to reboot and get the following. Oct 19 11:35:35 Tower emhttp: Unmounting disks... Oct 19 11:35:35 Tower emhttp: shcmd (6865): umount /mnt/disk1 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk1: target is busy Oct 19 11:35:35 Tower root: (In some cases useful info about processes that Oct 19 11:35:35 Tower root: use the device is found by lsof( or fuser(1).) Oct 19 11:35:35 Tower emhttp: shcmd (6866): umount /mnt/disk2 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk2: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6867): rmdir /mnt/disk2 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk2': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6868): umount /mnt/disk3 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk3: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6869): rmdir /mnt/disk3 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk3': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6870): umount /mnt/disk4 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk4: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6871): rmdir /mnt/disk4 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk4': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6872): umount /mnt/disk5 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk5: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6873): rmdir /mnt/disk5 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk5': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6874): umount /mnt/disk6 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk6: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6875): rmdir /mnt/disk6 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk6': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6876): umount /mnt/disk7 |& logger Oct 19 11:35:35 Tower root: umount: /mnt/disk7: mountpoint not found Oct 19 11:35:35 Tower emhttp: shcmd (6877): rmdir /mnt/disk7 |& logger Oct 19 11:35:35 Tower root: rmdir: failed to remove '/mnt/disk7': No such file or directory Oct 19 11:35:35 Tower emhttp: shcmd (6878): umount /mnt/cache |& logger Oct 19 11:35:35 Tower root: umount: /mnt/cache: target is busy Oct 19 11:35:35 Tower root: (In some cases useful info about processes that Oct 19 11:35:35 Tower root: use the device is found by lsof( or fuser(1).) Oct 19 11:35:35 Tower emhttp: Retry unmounting disk share(s)...[/move][/move][/move] I have had to do a shutdown -r now a few times. Not sure if this is related. Quote Link to comment
ryan8382 Posted October 19, 2016 Author Share Posted October 19, 2016 After doing that reboot and deleting the docker.img. Now it came up with docker started. I'm adding a container now to see if it is working and will post the diag later. No clue as to what happened. Quote Link to comment
Squid Posted October 19, 2016 Share Posted October 19, 2016 After doing that reboot and deleting the docker.img. Now it came up with docker started. I'm adding a container now to see if it is working and will post the diag later. No clue as to what happened. Some process was holding up the docker.img. it actually helps me out huge as now I have an idea of what to try if when it comes up again Sent from my LG-D852 using Tapatalk 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.