The Transplant Posted January 30 Share Posted January 30 Something happened last week, perhaps when I ran an update, and SABNZBD and SWAG just stopped working. When I start either of them they spin, I don't see any logs in the console and they stop. No popup to indicate an error. I removed SABNZBD and reinstalled it. Same thing. So I am not sure where to go from here. Here is a snippet of my log when I am trying to start the dockers. Port 2 and 6 I think are the dockers. Any suggestions? Thanks! Jan 30 12:05:57 Odin kernel: BTRFS warning (device loop2): csum failed root 6073 ino 687 off 638976 csum 0x2c38410a expected csum 0x8898c8d9 mirror 1 Jan 30 12:05:57 Odin kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 400, gen 0 Jan 30 12:05:57 Odin kernel: BTRFS warning (device loop2): csum failed root 6073 ino 687 off 638976 csum 0x2c38410a expected csum 0x8898c8d9 mirror 1 Jan 30 12:05:57 Odin kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 401, gen 0 Jan 30 12:05:57 Odin kernel: BTRFS warning (device loop2): csum failed root 6073 ino 687 off 638976 csum 0x2c38410a expected csum 0x8898c8d9 mirror 1 Jan 30 12:05:57 Odin kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 402, gen 0 Jan 30 12:05:57 Odin kernel: docker0: port 6(veth589fad8) entered disabled state Jan 30 12:05:57 Odin kernel: vethde2109e: renamed from eth0 Jan 30 12:05:57 Odin kernel: docker0: port 6(veth589fad8) entered disabled state Jan 30 12:05:57 Odin kernel: device veth589fad8 left promiscuous mode Jan 30 12:05:57 Odin kernel: docker0: port 6(veth589fad8) entered disabled state Jan 30 12:06:12 Odin sshd[37720]: Starting session: command for root from 192.168.2.54 port 62153 id 4 Jan 30 12:06:12 Odin sshd[37720]: Close session: user root from 192.168.2.54 port 62153 id 4 Jan 30 12:06:15 Odin kernel: br-d202c8e962dc: port 2(vetha2fa11f) entered blocking state Jan 30 12:06:15 Odin kernel: br-d202c8e962dc: port 2(vetha2fa11f) entered disabled state Jan 30 12:06:15 Odin kernel: device vetha2fa11f entered promiscuous mode Jan 30 12:06:15 Odin kernel: eth0: renamed from veth6c20db8 Jan 30 12:06:15 Odin kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha2fa11f: link becomes ready Jan 30 12:06:15 Odin kernel: br-d202c8e962dc: port 2(vetha2fa11f) entered blocking state Jan 30 12:06:15 Odin kernel: br-d202c8e962dc: port 2(vetha2fa11f) entered forwarding state Jan 30 12:06:15 Odin kernel: BTRFS warning (device loop2): csum failed root 6052 ino 687 off 638976 csum 0x2c38410a expected csum 0x8898c8d9 mirror 1 Jan 30 12:06:15 Odin kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 403, gen 0 Jan 30 12:06:15 Odin kernel: BTRFS warning (device loop2): csum failed root 6052 ino 687 off 638976 csum 0x2c38410a expected csum 0x8898c8d9 mirror 1 Jan 30 12:06:15 Odin kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 404, gen 0 Jan 30 12:06:15 Odin kernel: BTRFS warning (device loop2): csum failed root 6052 ino 687 off 638976 csum 0x2c38410a expected csum 0x8898c8d9 mirror 1 Jan 30 12:06:15 Odin kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 405, gen 0 Jan 30 12:06:16 Odin kernel: veth6c20db8: renamed from eth0 Jan 30 12:06:16 Odin kernel: br-d202c8e962dc: port 2(vetha2fa11f) entered disabled state Jan 30 12:06:16 Odin kernel: br-d202c8e962dc: port 2(vetha2fa11f) entered disabled state Jan 30 12:06:16 Odin kernel: device vetha2fa11f left promiscuous mode Jan 30 12:06:16 Odin kernel: br-d202c8e962dc: port 2(vetha2fa11f) entered disabled state Quote Link to comment
Solution JorgeB Posted January 30 Solution Share Posted January 30 Looks like the docker image is corrupt, but please post the complete diagnostics. Quote Link to comment
The Transplant Posted January 30 Author Share Posted January 30 1 hour ago, JorgeB said: Looks like the docker image is corrupt, but please post the complete diagnostics. Thanks @JorgeB. I have posted the diagnostic download in this message. odin-diagnostics-20240130-1400.zip Quote Link to comment
JorgeB Posted January 31 Share Posted January 31 Recreate the docker image: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks I would also like to see new diags after a reboot, since the ones you posted rotated due to a lot of spam. Quote Link to comment
The Transplant Posted February 5 Author Share Posted February 5 On 1/31/2024 at 4:01 AM, JorgeB said: Recreate the docker image: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks I would also like to see new diags after a reboot, since the ones you posted rotated due to a lot of spam. ok, I got around to doing this. It required a little work as I did have some custom networks, some of which I wasn't using, so this was a good way to clean this out. Things seem to be running a lot smoother now and I am able to load the dockers that were not working before. I wasn't sure if you wanted them after a reboot and before I rebuilt the image, or after I rebuilt the image. But they are attached after everything was rebuilt just in case. Thanks. odin-diagnostics-20240205-0727.zip Quote Link to comment
JorgeB Posted February 5 Share Posted February 5 If everything is working now no need for the diags. Quote Link to comment
Recommended Posts
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.