January 13, 20251 yr I did a few things at once unfortunately, and I think I broke something. First, I moved my unraid docker image from my disk to my cache. Then I upgraded to 7.0. Once I tried to restart, my disk1 was not being unmounted, and then Unraid forced a restart. Now, I'm getting the error below, and Docker will not start. I've attached my syslog. Please help. Jan 13 13:39:51 B650-7700x unraid-api[23991]: ✔️ UNRAID API started successfully! Jan 13 13:39:51 B650-7700x unraid-api[23991]: ⚠️ Caught exception: connect ECONNREFUSED /var/run/docker.sock Jan 13 13:39:51 B650-7700x unraid-api[23991]: ⚠️ UNRAID API crashed with exit code 1 Jan 13 13:39:57 B650-7700x unraid-api[25459]: ✔️ UNRAID API started successfully! Jan 13 13:39:57 B650-7700x unraid-api[25459]: ⚠️ Caught exception: connect ECONNREFUSED /var/run/docker.sock Jan 13 13:39:57 B650-7700x unraid-api[25459]: ⚠️ UNRAID API crashed with exit code 1 Jan 13 13:40:04 B650-7700x unraid-api[26762]: ✔️ UNRAID API started successfully! Jan 13 13:40:04 B650-7700x unraid-api[26762]: ⚠️ Caught exception: connect ECONNREFUSED /var/run/docker.sock Jan 13 13:40:04 B650-7700x unraid-api[26762]: ⚠️ UNRAID API crashed with exit code 1 b650-7700x-syslog-20250113-1842.zip Edited January 13, 20251 yr by i4ybrid
January 13, 20251 yr Author Sorry, I've attachd the diagnostics. b650-7700x-diagnostics-20250113-1349.zip
January 13, 20251 yr Author How can I get my docker configurations if I just delete my docker image and rebuild? I didn't back up my configurations unfortunately...
January 13, 20251 yr Community Expert Why do you think you need 250G docker.img? Default 20G is often more than enough. Delete docker.img and recreate at a more reasonable size. https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Then you can reinstall your containers from Previous Apps. https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
January 13, 20251 yr Community Expert Solution Jan 13 13:39:00 B650-7700x kernel: BTRFS warning (device loop2): csum failed root 5 ino 269 off 4096 csum 0xa700954d expected csum 0xacb6b47d mirror 1 Jan 13 13:39:00 B650-7700x kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 16, gen 0 Jan 13 13:39:00 B650-7700x kernel: BTRFS warning (device loop2): csum failed root 5 ino 269 off 4096 csum 0xa700954d expected csum 0xacb6b47d mirror 1 Jan 13 13:39:00 B650-7700x kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 17, gen 0 Jan 13 13:39:00 B650-7700x kernel: BTRFS warning (device loop2): csum failed root 5 ino 269 off 4096 csum 0xa700954d expected csum 0xacb6b47d mirror 1 Jan 13 13:39:00 B650-7700x kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 18, gen 0 csum errors on btrfs are usually bad RAM. Have you done memtest recently?
January 13, 20251 yr Author Thanks, I'll do this. I had a huge docker image because I was using stable-diffusion and a1111 doesn't seem to do too well with mounted drives. I'll reduce it down. Docker is back up after I deleted my image. Appreciate the help.
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.