b00 Posted March 4, 2022 Share Posted March 4, 2022 Hello guys, I have built together an unraid server- everything except the drives and RAM is new. It consists of three HDD's and one NVMe for cache. Today I started moving data (movies) from a PC to server. When I started moving the data from cache to HDD's I found out a bunch of these errors in the logs: Mar 4 12:26:00 Tower emhttpd: shcmd (561): /usr/local/sbin/mover &> /dev/null & Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4163620864 csum 0x7ed6589e expected csum 0xa07c1099 mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4164747264 csum 0xa80daef8 expected csum 0x0c17a62f mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4163620864 csum 0x7ed6589e expected csum 0xa07c1099 mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4163620864 csum 0x7ed6589e expected csum 0xa07c1099 mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 Mar 4 12:28:03 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 276 off 4163620864 csum 0x7ed6589e expected csum 0xa07c1099 mirror 1 Mar 4 12:28:03 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 Mar 4 12:28:04 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 278 off 558874624 csum 0x59e3aa3e expected csum 0xfdf9a2e9 mirror 1 Mar 4 12:28:04 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 6, gen 0 Mar 4 12:28:04 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 278 off 558874624 csum 0x59e3aa3e expected csum 0xfdf9a2e9 mirror 1 Mar 4 12:28:04 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 Mar 4 12:28:04 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 278 off 558874624 csum 0x59e3aa3e expected csum 0xfdf9a2e9 mirror 1 Mar 4 12:28:04 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Mar 4 12:28:04 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 278 off 558874624 csum 0x59e3aa3e expected csum 0xfdf9a2e9 mirror 1 I'm not sure what to do with it. Does it mean that my new NVMe is failing? Can I test it somehow? Should I delete all the data transferred from cache to hdd and transfer them again? I'm not using any docker or apps yet (I've only used the preclear plugin on the hdd's on different pc) tower-diagnostics-20220304-1244.zip tower-syslog-20220304-1144.zip Quote Link to comment
JorgeB Posted March 4, 2022 Share Posted March 4, 2022 Checksum errors mean btrfs is detecting data corruption, start by running memtest. Quote Link to comment
b00 Posted March 5, 2022 Author Share Posted March 5, 2022 Wow, @JorgeB it looks You were right! I would never thought that it was the RAM problem. Since most of my hardware is re-used (motherboard, CPU, PSU) i need to double check if the problem is the memory (which is new) or a CPU/mobo. Thanks for pointing me into that direction. 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.