November 27, 20241 yr Not sure how to troubleshoot this. I've had problems in the past when my cache was BTRFS. I would get periodic log tree corruptions. When Unraid began supporting ZFS I formatted the cache to ZFS and it was fine for many many months. Last month my Docker containers went down and I saw a BTRFS error in the server log. I disregarded it and restarted the server, everything fixed itself. It's happened again today and multiple restarts later, Docker will not start. Steps I've taken to remedy: rescue zero-log command (says no valid BTRFS found), restarts, reseating cache drive, reseating memory, confirming memory speed (too fast causes me problems), safe mode. Notes: The VM manager appears to be working just fine. I have a windows VM running exclusively on the cache drive and it appears unaffected. Browsing SMB shares located on the cache works fine too. Attached is my diag. Version 6.12.10. If URbackup has been doing its job I'll have proper backups of what I care about from the windows VM. I have appdata backup plugin running as well so docker container info is covered too. waffle-diagnostics-20241126-2103.zip
November 27, 20241 yr Community Expert Solution The BTRFS errors are coming from the loop2 device which is where you docker image is mounted (by default this is formatted as BTRFS internally). It is not clear why this is happening. Since it looks like the docker.img file may well be corrupt, I suggest that you recreate the docker.img file and then reload your containers with settings intact via Apps->Previous apps.
November 27, 20241 yr Author 14 hours ago, itimpi said: The BTRFS errors are coming from the loop2 device which is where you docker image is mounted (by default this is formatted as BTRFS internally). It is not clear why this is happening. Since it looks like the docker.img file may well be corrupt, I suggest that you recreate the docker.img file and then reload your containers with settings intact via Apps->Previous apps. Thanks! I was curious why the device was loop2 instead of the original nvme0n1p1. I did try recsuing zero-log those devices, but was met with the "this isn't a btrfs file system" message.
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.