My Cache drive had filled up so I manually invoked the Mover from the main page.  Sometime during the move the dockers became unavailable and even now that the move is complete, the docker service is showing errors and can not start.

 

I have tried stopping and starting the docker service from the settings page but I'm afraid to actually stop the server itself.

 

 

 

 

The server log is filling up with errors like this:

 

Jun 11 14:42:19 Tower kernel: BTRFS info (device loop2): no csum found for inode 3871 start 0
Jun 11 14:42:19 Tower kernel: BTRFS warning (device loop2): csum failed root 8166 ino 3871 off 0 csum 0x2cfa2d2f expected csum 0x00000000 mirror 1
Jun 11 14:42:19 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 190029, gen 0
Jun 11 14:42:20 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 32727040000 wanted 809781 found 807749
Jun 11 14:42:20 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 32727040000 wanted 809781 found 807749
Jun 11 14:42:20 Tower kernel: BTRFS info (device loop2): no csum found for inode 1066 start 0
Jun 11 14:42:20 Tower kernel: BTRFS warning (device loop2): csum failed root 8081 ino 1066 off 0 csum 0x0f8afbf7 expected csum 0x00000000 mirror 1
Jun 11 14:42:20 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 190030, gen 0
Jun 11 14:42:29 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 32726908928 wanted 809781 found 807749
Jun 11 14:42:29 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 32726908928 wanted 809781 found 807749

 

tower-diagnostics-20220611-1437.zip

After a server reboot the docker service started with no issues.  Parity check is still running but I'm not sure what the previous errors are pointing to.

Problems with the docker image, apparently from running out of space, run a scrub on the docker image, or in doubt just delete and re-create it.