January 21, 20251 yr Jan 21 13:44:51 Snuts emhttpd: shcmd (301): /usr/local/sbin/mount_image '/mnt/nvme_cache/system/docker/docker.img' /var/lib/docker 60 Jan 21 13:44:51 Snuts kernel: loop3: detected capacity change from 0 to 125829120 Jan 21 13:44:51 Snuts kernel: BTRFS: device fsid 0e6e0292-448f-4925-96e5-da45dc1abebf devid 1 transid 4862398 /dev/loop3 scanned by mount (82182) Jan 21 13:44:51 Snuts kernel: BTRFS info (device loop3): first mount of filesystem 0e6e0292-448f-4925-96e5-da45dc1abebf Jan 21 13:44:51 Snuts kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm Jan 21 13:44:51 Snuts kernel: BTRFS info (device loop3): using free space tree Jan 21 13:44:51 Snuts kernel: BTRFS error (device loop3): bad tree block start, mirror 1 want 72966422528 have 0 Jan 21 13:44:51 Snuts kernel: BTRFS error (device loop3): bad tree block start, mirror 2 want 72966422528 have 0 Jan 21 13:44:51 Snuts kernel: BTRFS warning (device loop3): couldn't read tree root Jan 21 13:44:51 Snuts root: mount: /var/lib/docker: can't read superblock on /dev/loop3. Jan 21 13:44:51 Snuts root: dmesg(1) may have more information after failed mount system call. Jan 21 13:44:51 Snuts kernel: BTRFS error (device loop3): open_ctree failed Jan 21 13:44:51 Snuts root: mount error Jan 21 13:44:51 Snuts emhttpd: shcmd (301): exit status: 1 snuts-diagnostics-20250121-1341.zip I was trying to tinker with Mover Tuning to get it back to behaving how it should. It seemed to get a little wonky after I updated to 7.0.0. the other day. But after rebooting I saw errors and a message on the Docker tab that "Docker Service failed to start" I am attaching Diagnostics. Do I need to delete and rebuild my Docker image? Is it a pain? I was using custom networks for some containers but they were created so long ago I forget which containers had them or what they even were. I think i am about to be a very sad camper. Edited January 21, 20251 yr by DontWorryScro accidentally attached syslog and not diagnostics
January 22, 20251 yr Community Expert Solution Recreate the docker image: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Then: https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
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.