After disabling and re-enabling Docker in the settings to try to get it back online the the log it read:

Quote

Sep 2 16:04:23 hyperserver4 root: Starting Samba: /usr/sbin/nmbd -D
Sep 2 16:04:23 hyperserver4 root: /usr/sbin/smbd -D
Sep 2 16:04:23 hyperserver4 root: /usr/sbin/winbindd -D
Sep 2 16:04:23 hyperserver4 emhttpd: shcmd (45017): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20
Sep 2 16:04:23 hyperserver4 root: /mnt/user/system/docker/docker.img is in-use, cannot mount
Sep 2 16:04:23 hyperserver4 emhttpd: shcmd (45017): exit status: 1

What's using that? I wasn't even aware of that location. I'm not Docker-savvy...like at all.

 

The server stopped responding a couple of day ago and I had to hard reset it, there was a huge BT transfer going on, the client running on my computer downloading to the networked storage; just right now I kept noticing after trying to restart it quickly failed and the BitTorrent client showed a permissions message so over SSH I did "chmod -vfR 777 ." in the root of the affected directory and the client continued downloading, however, that was a permissions denied thing, not file in-use. Is it related? Should I try to manually set right the permissions?

 

If so, what are the proper permissions?

 

Oh BTW, the server was running on trial still, so naturally at restart it wouldn't come back, I got a license but got a little busy and it took me like a day or two to actually put it in and I haven't restarted the server since because the parity check was still running.

 

Thanks for your help !

Hi there,

 

Can you please attach you full system diagnostics?  You can get those from the Tools > Diagnostics page.  This will give us more information to help troubleshoot the issue.

This is the Docker info I found in it:

 

./logs/docker.txt

Quote

time="2019-09-02T00:29:40.714401268-06:00" level=error msg="Handler for GET /v1.37/containers/1d3e957ae34bb7feefc078e5f974cf6b427fa309e3cef3a7867fe14c85e6b9dd/json returned error: write unix /var/run/docker.sock->@: write: broken pipe"
2019-09-02 00:29:40.714472 I | http: multiple response.WriteHeader calls
time="2019-09-02T13:43:27.345708673-06:00" level=error msg="transport: loopyWriter.run returning. Err: connection error: desc = \"transport is closing\"" module=grpc
time="2019-09-02T13:43:27.346169072-06:00" level=error msg="transport: loopyWriter.run returning. Err: connection error: desc = \"transport is closing\"" module=grpc
time="2019-09-02T13:43:27.346488465-06:00" level=error msg="transport: loopyWriter.run returning. Err: connection error: desc = \"transport is closing\"" module=grpc
time="2019-09-02T13:59:33.201003205-06:00" level=error msg="c61df9fa08c57f17c06e79cbb5fd02c27cb310e5f5912072f3961acde8742b25 cleanup: failed to delete container from containerd: no such container"
time="2019-09-02T13:59:48.203891772-06:00" level=error msg="Force shutdown daemon"
time="2019-09-02T13:59:48.204058760-06:00" level=error msg="transport: loopyWriter.run returning. Err: connection error: desc = \"transport is closing\"" module=grpc
time="2019-09-02T13:59:48.204591195-06:00" level=error msg="transport: loopyWriter.run returning. Err: connection error: desc = \"transport is closing\"" module=grpc
time="2019-09-02T13:59:48.204591789-06:00" level=error msg="transport: loopyWriter.run returning. Err: connection error: desc = \"transport is closing\"" module=grpc

./config/docker.cfg

Quote

DOCKER_ENABLED="yes"
DOCKER_IMAGE_FILE="/mnt/user/system/docker/docker.img"
DOCKER_IMAGE_SIZE="20"
DOCKER_APP_CONFIG_PATH="/mnt/user/appdata/"
DOCKER_APP_UNRAID_PATH=""
DOCKER_CUSTOM_NETWORKS=" "
DOCKER_LOG_ROTATION="yes"
DOCKER_LOG_SIZE="50m"
DOCKER_LOG_FILES="1"
DOCKER_AUTHORING_MODE="no"
DOCKER_USER_NETWORKS="remove"

Thanks for answering.

hyperserver4-diagnostics-20190905-2248.zip

Edited September 5, 20196 yr by vitaprimo

Well, this is embarrassing… 🙄

 

I just restarted the server using this little button:

…and I got the list of the containers back, I went to the Docker section and got:

 

Yeah…my bad. 🤤😝

 

It just needed a simple restart. It triggered parity check, which says it will complete in two days but I got my containers back! ❤️ I can now order new disks and take this server into "production".

 

Thanks anyway !