CyberMew Posted January 10 Share Posted January 10 Hi. I am getting some errors in log, not sure why, I think my docker containers all stopped due to backup (not sure), but it is not resuming and I don't see the weekly backup that it usually runs. Quote Jan 9 04:55:41 Tower kernel: BTRFS info (device loop4): no csum found for inode 3887 start 237568 Jan 9 04:55:41 Tower kernel: BTRFS warning (device loop4): csum failed root 396 ino 3887 off 237568 csum 0x7f0a4dc5 expected csum 0x00000000 mirror 1 Jan 9 04:55:41 Tower kernel: BTRFS error (device loop4): bdev /dev/loop4 errs: wr 0, rd 0, flush 0, corrupt 46726, gen 0 Jan 9 04:55:41 Tower kernel: BTRFS error (device loop4): tree first key mismatch detected, bytenr=196624384 parent_transid=235 key expected=(18446744073709535222,128,5549367296) has=(18446744073709551606,128,5549367296) Jan 9 04:55:41 Tower kernel: BTRFS error (device loop4): tree first key mismatch detected, bytenr=196624384 parent_transid=235 key expected=(18446744073709535222,128,5549367296) has=(18446744073709551606,128,5549367296) Any idea what is the issue and how to fix it? tower-diagnostics-20240110-2303.zip Quote Link to comment
JorgeB Posted January 10 Share Posted January 10 Docker image is corrupt, delete and recreate. Quote Link to comment
CyberMew Posted January 10 Author Share Posted January 10 Thank you! Glad to hear it isn’t something with the file system… any idea why it got corrupted in the first place..? Quote Link to comment
JorgeB Posted January 10 Share Posted January 10 Not really, especially since the syslog already rotated, but as long as it's not a frequent problem there may not be an underlying issue. 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.