Not sure what happened here...was doing a large backup to CrashPlan cloud...not sure if that had anything to do with it but then Docker stopped working and won't reload.

 

I've tried rebooting the system, disabling Docker and erasing the img file and restarting it but no luck.

 

Here's what the log says:

 

Quote

Oct 2 20:11:35 tower root: failed to create image file
Oct 2 20:11:35 tower emhttpd: shcmd (122): exit status: 1
Oct 2 20:12:17 tower emhttpd: req (5): cmd=/plugins/community.applications/scripts/updatePLG.sh&arg1=community.applications.plg&csrf_token=****************
Oct 2 20:12:17 tower emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/updatePLG.sh community.applications.plg
Oct 2 20:12:22 tower root: plugin: running: anonymous
Oct 2 20:12:22 tower root: plugin: running: anonymous
Oct 2 20:12:22 tower root: plugin: creating: /boot/config/plugins/community.applications/community.applications-2018.10.02.txz - downloading from URL https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2018.10.02.txz
Oct 2 20:12:22 tower root: plugin: checking: /boot/config/plugins/community.applications/community.applications-2018.10.02.txz - MD5
Oct 2 20:12:22 tower root: plugin: running: /boot/config/plugins/community.applications/community.applications-2018.10.02.txz
Oct 2 20:12:22 tower root: plugin: running: anonymous
Oct 2 20:13:09 tower ool www[14631]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update
Oct 2 20:13:09 tower emhttpd: req (6): cmdStatus=apply&csrf_token=****************
Oct 2 20:13:09 tower emhttpd: Starting services...
Oct 2 20:13:17 tower ool www[14631]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update
Oct 2 20:13:17 tower emhttpd: req (7): cmdStatus=apply&csrf_token=****************
Oct 2 20:13:17 tower emhttpd: Starting services...
Oct 2 20:13:17 tower emhttpd: shcmd (150): /usr/local/sbin/mount_image '/mnt/user/docker/docker.img' /var/lib/docker 40
Oct 2 20:13:17 tower root: Creating new image file: /mnt/user/docker/docker.img size: 40G
Oct 2 20:13:17 tower shfs: error: shfs_create, 2074: No medium found (123): assign_disk: docker/docker.img
Oct 2 20:13:17 tower root: touch: cannot touch '/mnt/user/docker/docker.img': No medium found
Oct 2 20:13:17 tower shfs: error: shfs_create, 2074: No medium found (123): assign_disk: docker/docker.img
Oct 2 20:13:17 tower shfs: error: shfs_create, 2074: No medium found (123): assign_disk: docker/docker.img
Oct 2 20:13:17 tower root: failed to create image file
Oct 2 20:13:17 tower emhttpd: shcmd (150): exit status: 1
Oct 2 20:16:42 tower ool www[14631]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update
Oct 2 20:16:43 tower emhttpd: req (8): cmdStatus=apply&csrf_token=****************
Oct 2 20:16:43 tower emhttpd: Starting services...
Oct 2 20:17:16 tower ool www[19174]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update
Oct 2 20:17:16 tower emhttpd: req (9): cmdStatus=apply&csrf_token=****************
Oct 2 20:17:16 tower emhttpd: Starting services...
Oct 2 20:17:16 tower emhttpd: shcmd (182): /usr/local/sbin/mount_image '/mnt/user/docker/docker.img' /var/lib/docker 40
Oct 2 20:17:16 tower root: Creating new image file: /mnt/user/docker/docker.img size: 40G
Oct 2 20:17:16 tower shfs: error: shfs_create, 2074: No medium found (123): assign_disk: docker/docker.img
Oct 2 20:17:16 tower root: touch: cannot touch '/mnt/user/docker/docker.img': No medium found
Oct 2 20:17:16 tower shfs: error: shfs_create, 2074: No medium found (123): assign_disk: docker/docker.img
Oct 2 20:17:16 tower shfs: error: shfs_create, 2074: No medium found (123): assign_disk: docker/docker.img
Oct 2 20:17:16 tower root: failed to create image file
Oct 2 20:17:16 tower emhttpd: shcmd (182): exit status: 1

 

 

Any help?

Im not experiensed in reading the log files. However it looks like the disk containing the docker is missing.

Sent from my SM-G955F using Tapatalk

Yet I can browse to it....

The post your diagnostics

On 10/3/2018 at 3:45 PM, Squid said:

The post your diagnostics

Thanks Squid. Appreciated as always.

tower-diagnostics-20181004-2013.zip

You don't have a cache drive installed or recognized.  The docker.img is trying to load from the cache drive, but since it doesn't exist, then no-go

 

Probably it dropped offline when your system crashed (On the 2nd?), and never came back alive for whatever reason.  If its still physically present, then reseat the cabling.

That did it, thanks Squid.  Can't believe I didn't notice cache drive missing...*palmface*