August 13, 20214 yr I found some of my dockers not working this morning, when I go to check the unraid logs it shows these errors. I found a post by Squid where he suggested deleting the docker image and reinstalling the dockers. I did this following his steps, and when I went to start them up again the docker services wouldn't start. Not know what else I could do I decided to do a clean reboot of the server. When the server came back online a parity check was started, and all of my dockers started and were running without error. On one hand I am happy everything is working, but I would like help to figure out why this happened in the first place, so that I could avoid it. I did download my diagnostics before rebooting, so hopefully that helps. 03:09:19 Skynet kernel: BTRFS info (device loop2): no csum found for inode 8016 start 0 Aug 13 03:09:19 Skynet kernel: BTRFS warning (device loop2): csum failed root 2905 ino 8016 off 0 csum 0xb0d03f8f expected csum 0x00000000 mirror 1 Aug 13 03:09:19 Skynet kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 58, rd 0, flush 0, corrupt 43796, gen 0 Aug 13 03:09:19 Skynet kernel: BTRFS error (device loop2): parent transid verify failed on 8222932992 wanted 1195432 found 1195419 Aug 13 03:09:19 Skynet kernel: BTRFS error (device loop2): parent transid verify failed on 8222932992 wanted 1195432 found 1195419 Aug 13 03:09:19 Skynet kernel: BTRFS info (device loop2): no csum found for inode 8016 start 0 Aug 13 03:09:19 Skynet kernel: BTRFS warning (device loop2): csum failed root 2905 ino 8016 off 0 csum 0xb0d03f8f expected csum 0x00000000 mirror 1 Aug 13 03:09:19 Skynet kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 58, rd 0, flush 0, corrupt 43797, gen 0 Aug 13 03:09:20 Skynet kernel: BTRFS info (device loop2): no csum found for inode 8016 start 0 skynet-diagnostics-20210813-0500.zip
August 13, 20214 yr Community Expert There's filesystem corruption on this pool: Aug 13 00:27:49 Skynet kernel: BTRFS error (device sdb1): block=1476820992 write time tree block corruption detected This error usually indicates bad RAM or other kernel memory corruption, you should run memtest.
August 13, 20214 yr Author 3 minutes ago, JorgeB said: There's filesystem corruption on this pool: Aug 13 00:27:49 Skynet kernel: BTRFS error (device sdb1): block=1476820992 write time tree block corruption detected This error usually indicates bad RAM or other kernel memory corruption, you should run memtest. Is it possible to do that through the unraid GUI? I don't have a video out on my MOBO
August 13, 20214 yr Community Expert 4 minutes ago, Neldonado said: Is it possible to do that through the unraid GUI? No, it is possible to boot to memtest by changing the menu but then you couldn't see the results anyway, you need a monitor/ipmi.
August 13, 20214 yr Author 2 minutes ago, JorgeB said: No, it is possible to boot to memtest by changing the menu but then you couldn't see the results anyway, you need a monitor/ipmi. Is it ok to let parity check finish? I will have to remove one of my drives/ pcie card to put a video card in.
August 13, 20214 yr Community Expert It's OK, but if it's a correcting check and there is a RAM issue it can corrupt parity, no problem if it's non correcting.
August 13, 20214 yr Author 5 minutes ago, JorgeB said: It's OK, but if it's a correcting check and there is a RAM issue it can corrupt parity, no problem if it's non correcting. Yeah, everything looks good so far. I am hoping it is ram related, that would be an easy fix. I had some Corruption issues a few weeks ago too. (you can see my other posts) however this isn't as bad because I don't think any data was lost, and I am pretty sure it was bad drive related. Edited August 13, 20214 yr by Neldonado clarification
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.