May  8 22:32:58 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420370, gen 0
May  8 22:33:31 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 100152063 off 1343488 csum 0xfb571968 expected csum 0x15800c92 mirror 1
May  8 22:33:31 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420371, gen 0
May  8 22:38:32 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 100152063 off 1343488 csum 0xfb571968 expected csum 0x15800c92 mirror 1
May  8 22:38:32 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420372, gen 0
May  8 22:38:32 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 100152063 off 1343488 csum 0xfb571968 expected csum 0x15800c92 mirror 1
May  8 22:38:32 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420373, gen 0
May  8 22:38:33 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 100152063 off 1343488 csum 0xfb571968 expected csum 0x15800c92 mirror 1
May  8 22:38:33 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420374, gen 0
May  8 22:38:33 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 100152063 off 1343488 csum 0xfb571968 expected csum 0x15800c92 mirror 1
May  8 22:38:33 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420375, gen 0
May  8 22:38:38 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 100152063 off 1343488 csum 0xfb571968 expected csum 0x15800c92 mirror 1
May  8 22:38:38 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420376, gen 0
May  8 22:38:38 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 100152063 off 1343488 csum 0xfb571968 expected csum 0x15800c92 mirror 1
May  8 22:38:38 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420377, gen 0
May  8 22:38:38 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 100152063 off 1343488 csum 0xfb571968 expected csum 0x15800c92 mirror 1
May  8 22:38:38 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420378, gen 0
May  8 22:40:26 Tower kernel: BTRFS warning (device sdc1): csum failed root 5 ino 100152063 off 1343488 csum 0xfb571968 expected csum 0x15800c92 mirror 1
May  8 22:40:26 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 14420379, gen 0

 

Good Evening,

 

I am seeing the above errors coming through my server when I view the cache log. I am looking for any information on what could be causing (is it a cache disk going bad, some other issue, etc) My cache is on an SSD albeit not a super new SSD, but an ADATA drive. Do these errors matter, are they causing issues, could I be losing data, etc are all my questions.

 

Looking for the way forward here. Any and all information helps. My RAM is running at 2133 (I thought maybe it was a RAM issue based on other forum posts but as seen above the warnings and errors reference SDC1, my cache device.)

 

Edit to add: I have run a scrub and no errors are found. I am not noticing any degradation to my server functionality but the errors concern me because they look scary.

Edited May 9, 20233 yr by getty
More information

Please post the diagnostics.

9 hours ago, JorgeB said:

Please post the diagnostics.

Attached here. Thank you for looking into this with me! tower-diagnostics-20230509-1213.zip

This is usually RAM related, start by running memtest.

17 minutes ago, JorgeB said:

This is usually RAM related, start by running memtest.

Ok I'll give it a go tonight. Just pick the memtest86+ option at boot? Is there anything I should be looking for to post here for results? 

4 minutes ago, getty said:

Just pick the memtest86+ option at boot?

Yes, it only works with legacy/CSM boot, if you can only boot UEFI use the free Passmark memtest.

10 hours ago, JorgeB said:

Yes, it only works with legacy/CSM boot, if you can only boot UEFI use the free Passmark memtest.

Currently running the memtest off a USB as I'm UEFI. It doesn't appear to be finding any errors though. 

 

Edit: memtest completed and is reporting 0 errors or ECC errors. 

Edited May 10, 20233 yr by getty

Then and if the scrub didn't find any errors reset the fs stats and keep monitoring, see here for how to do that.

6 hours ago, JorgeB said:

Then and if the scrub didn't find any errors reset the fs stats and keep monitoring, see here for how to do that.

Awesome! I will keep an eye on it but the errors seem to have stopped. I was able to locate 2 files causing csum errors in my cache scrub. I deleted them and let them be rebuilt by Docker, rescrubbed, and ran the script to clear errors and it is all ok for now. Thanks so much for the assistance! Will probably look into an M.2 replacement for cache sooner than later.