December 29, 20241 yr After a recent restart Docker won't start. I tried stopping the array, as well as restarting completely. I even attempted to manually restart my daemon which yielded this: root@STower24:~# /etc/rc.d/rc.docker stop rc.docker: Stopping containers... rc.docker: Stopping network... rc.docker: Stopping Docker daemon... rc.docker: Docker daemon... Already stopped. root@STower24:~# /etc/rc.d/rc.docker start rc.docker: Starting Docker daemon... rc.docker: Docker daemon... No image mounted at /var/lib/docker. rc.docker: Starting network... stower24-diagnostics-20241229-1752.zip
December 29, 20241 yr Community Expert Solution Seems like your docker image file has an issue Dec 29 17:31:16 STower24 kernel: BTRFS error (device loop2): parent transid verify failed on logical 7820394496 mirror 1 wanted 645367 found 645369 Dec 29 17:31:16 STower24 kernel: BTRFS error (device loop2): parent transid verify failed on logical 7820394496 mirror 2 wanted 645367 found 645369 Dec 29 17:31:16 STower24 kernel: BTRFS error (device loop2): failed to read block groups: -5 Dec 29 17:31:16 STower24 root: mount: /var/lib/docker: can't read superblock on /dev/loop2. took a bit to find https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Edited December 29, 20241 yr by Mainfrezzer
January 14, 20251 yr Author Thanks. It keeps happening with BTRFS. Already had changed my cache SSD to XFS a few months back due to other issues. Now I did the same for my Docker image. Has been more stable so far.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.