Hey,

 

I recently moved my unraid server to a new location, and had a few disks fail during the move. I replaced the drives and created a new config, and everything appears to be fine with the array. The first time I rebooted after recreating the array, docker started up correctly. Once it was working, I turned it off again and installed a 10GB NIC. After booting with the new NIC, I received the docker service failed to start message. A reboot fixed it once, but on subsequent reboots it's fails to start every time.

 

I have verified that I can mount the image myself. I've also tried renaming the existing docker disk and creating a new one, but the same issue occurs with the new one. There is still 1 bad disk in the system, but it is removed from the array.

 

I've attached the diag from before rebooting.

 

 

diag.zip

Looking at the docker logs, it looks like the issue is related to this error:

 

 failed to start daemon: Devices cgroup isn't mounted

 

I do see cgroups in my mounts:

 

I was able to start docker after manually mounting cgroups based on the discussion here:

 

https://stackoverflow.com/questions/32002882/error-starting-docker-daemon-on-ubuntu-14-04-devices-cgroup-isnt-mounted

 

To mount it manually I ran:

 

mkdir /sys/fs/cgroup/devices

mount -t cgroup -o devices devices /sys/fs/cgroup/devices

 

I'd still like to understand why it wasn't mount properly if anyone has any insight.

 

Thanks

You need to look at 35000cca03873dc20-20230513-1524  (sdv)

 

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:          0  2969053         0   2969053    3245083     112984.041       40497
write:         0  4392645         0   4392645        532      96506.348           0
verify:        0  5820404         0   5820404       4866      52443.584           0

Tons of errors related to this drive

 

Not sure right now why you're seeing the docker issue tho