Hello Guys,

 

I recently have some trouble on my server which started when my array storage and cache got completely full. 

 

Since then I have trouble shutting down / rebooting the server.

 

I did some digging and found this thread which pointed me in the right direction why the array cant shut down: https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/page/3/

 

I found out that /dev/loop2 does not unmount automatically, when I do it manually with "umount /dev/loop2" the server reboots just fine.

 

I have increased the storage already so the cache isnt completely full again but the Docker service still refuses to start and I cant figure out why. (Im not that familiar with linux..)

 

Feb 16 19:31:25 Ame root: Resize device id 1 (/dev/loop3) from 30.00GiB to max 
Feb 16 19:31:25 Ame emhttpd: shcmd (132): /etc/rc.d/rc.docker start
Feb 16 19:31:25 Ame rc.docker: Starting Docker daemon...
Feb 16 19:31:28 Ame kernel: Bridge firewalling registered
Feb 16 19:32:02 Ame rc.docker: Docker daemon...  Failed.
Feb 16 19:32:02 Ame rc.docker: Starting network...
Feb 16 19:32:02 Ame rc.docker: Starting containers...
Feb 16 19:32:02 Ame emhttpd: shcmd (134): umount /var/lib/docker
Feb 16 19:32:02 Ame root: umount: /var/lib/docker: target is busy.
Feb 16 19:32:02 Ame emhttpd: shcmd (134): exit status: 32

 

I have added the diagnostics right after a clean reboot and trying to start the docker service, so I you can point me in the right direction to get this sorted.

 

Thanks!

 

 

 

ame-diagnostics-20250216-1932.zip

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications

 

https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Thank you! Deleting the docker image and reinstalling worked like a charm.