I have my server start the parity check at 3am on the 1st of the month.   My server had stopped responding when I got up today.   I wasn't able to ssh into it.   Bring up the web interface or anything.   I resorted to a reboot.  Once I rebooted, it started without the docker.    On the docker tab it shows "Docker Service failed to start."

 

Unraid 6.12.6

h/w: Supermicro X8SIL, Xeon  x3470, 32 GiB DDR3 Single-bit ECC, WD 8TB, HItachi 1TB, Toshiba 3TB, WD 8TB parity, SPCC 256gb cache

 

 

I noticed a couple BTRFS errors for loop2 in the log from the main Unraid page.  

 

This post below  looks promising but I don't understand enough to know if that would fix it or worsen it.  Also I started the parity check again so I wasn't sure if I should let it finish before I start trying to get the docker back or if I can stop the parity check without issues.

 

 

Any thoughts would be helpful.

Thank you

 

tower-diagnostics-20240601-1034.zip

Corrupt docker.img

 

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

 

Also you should fix

Jun  1 10:34:02 Tower root: Fix Common Problems: Warning: Share appdata set to cache-only, but files / folders exist on the array
Jun  1 10:34:02 Tower root: Fix Common Problems: Warning: Share tempjunk set to not use the cache, but files / folders exist on the cache drive
Jun  1 10:34:03 Tower root: Fix Common Problems: Warning: Plugin unassigned.devices.plg is not up to date

 

Thank you for the help with this.  Following the links was easy to recreate the docker.img

 

One note,  I had a custom network for a couple of the docker apps.   When the app was restored it listed the custom network as "none".    The next section from the second link discusses the custom networks.  What I ended up doing was before I started the app again I made sure to  create the custom network again.  I then updated/edited the container to use the custom network in the app settings.     Once changed, the app worked like before.