July 15, 20241 yr I am at a loss on how to go out solving this issue. Please help Jul 15 11:37:44 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 2797, rd 0, flush 0, corrupt 830, gen 0 Jul 15 11:37:49 Tower kernel: loop: Write error at byte offset 3429310464, length 4096. Jul 15 11:37:49 Tower kernel: loop: Write error at byte offset 5946294272, length 4096. Jul 15 11:37:49 Tower kernel: loop: Write error at byte offset 5946048512, length 4096. Jul 15 11:37:49 Tower kernel: loop: Write error at byte offset 3870638080, length 4096. Jul 15 11:37:49 Tower kernel: I/O error, dev loop2, sector 6697872 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jul 15 11:37:49 Tower kernel: I/O error, dev loop2, sector 11613856 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jul 15 11:37:49 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 2798, rd 0, flush 0, corrupt 830, gen 0 Jul 15 11:37:49 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 2799, rd 0, flush 0, corrupt 830, gen 0 Jul 15 11:37:49 Tower kernel: I/O error, dev loop2, sector 11613376 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jul 15 11:37:49 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 2800, rd 0, flush 0, corrupt 830, gen 0 Jul 15 11:37:49 Tower kernel: I/O error, dev loop2, sector 7559840 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jul 15 11:37:49 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 2801, rd 0, flush 0, corrupt 830, gen 0 Jul 15 11:37:49 Tower kernel: loop: Write error at byte offset 3870650368, length 4096. Jul 15 11:37:49 Tower kernel: loop: Write error at byte offset 5946843136, length 4096. Jul 15 11:37:49 Tower kernel: I/O error, dev loop2, sector 7559864 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jul 15 11:37:49 Tower kernel: loop: Write error at byte offset 5946388480, length 4096. Jul 15 11:37:49 Tower kernel: I/O error, dev loop2, sector 11614928 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jul 15 11:37:49 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 2802, rd 0, flush 0, corrupt 830, gen 0 Jul 15 11:37:49 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 2803, rd 0, flush 0, corrupt 830, gen 0 tower-diagnostics-20240715-1110.zip
July 15, 20241 yr Community Expert Solution This error write time tree block corruption detected Usually means bead RAM, so a good idea to run memtest. If nothing is found, and note that memtest is only definitive if it finds errors, try recreating the docker image: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Then: https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
July 15, 20241 yr Community Expert 58 minutes ago, JorgeB said: Usually means bead RAM, so a good idea to run memtest. I wonder if it is time to start suggesting using the "Live Memory Tester" plugin as well as using memtest? It would be nice to get some statistics on how often people actually do have RAM issues and how often that plugin indicates this.
July 15, 20241 yr Author I had recently upgraded to 128 gb from 32 gb ram. It looks like those sticks are causing the issue. I will contact RMA and get them replaced. In the meanwhile I have put my old 32 gb ram sticks and started a memtest on them just in case. Thank You @JorgeB for your help.
July 15, 20241 yr Community Expert 29 minutes ago, itimpi said: It would be nice to get some statistics on how often people actually do have RAM issues and how often that plugin indicates this. Yeah, when the plugin was released I was going to test with a known bad DIMM I had, unfortunately could not find it, I suspect that it may not be as good as memtest since it won't be able to test all the RAM, but it may still be useful and able to find issues when the problem is evident, like in the case above.
July 15, 20241 yr Community Expert 5 minutes ago, JorgeB said: Yeah, when the plugin was released I was going to test with a known bad DIMM I had, unfortunately could not find it, I suspect that it may not be as good as memtest since it won't be able to test all the RAM, but it may still be useful and able to find issues when the problem is evident, like in the case above. I know it cannot test all the RAM but I was wondering if it might pick up some issues that memtest does not as it can be run with Unraid executing its typical workload. Certainly a lot less hassle to run. A bit like you I would like to have some know 'bad' or 'borderline' RAM that could be used in a test environment to start comparing the plugin results with memtest ones.
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.