February 25, 20224 yr I got these log errors, its on my cache drive for my unraid server. Should I be worried? Feb 25 02:01:08 Tower emhttpd: read SMART /dev/sdd Feb 25 02:01:08 Tower emhttpd: read SMART /dev/sde Feb 25 02:01:23 Tower emhttpd: read SMART /dev/sdl Feb 25 02:13:01 Tower emhttpd: read SMART /dev/sdi Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 27, gen 0 Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2717736960 csum 0x9f9a8839 expected csum 0x9f1a8839 mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 28, gen 0 Feb 25 02:15:56 Tower shfs: copy_file: /mnt/cache/TV_Tower/Star Trek- Discovery/Season 4/Star Trek - Discovery - S04E10 - The Galactic Barrier.mkv /mnt/disk4/TV_Tower/Star Trek- Discovery/Season 4/Star Trek - Discovery - S04E10 - The Galactic Barrier.mkv.partial (5) Input/output error Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 29, gen 0 Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 30, gen 0 Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 31, gen 0 Feb 25 02:15:56 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:15:56 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 32, gen 0 Feb 25 02:16:11 Tower emhttpd: read SMART /dev/sdb Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 33, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2717736960 csum 0x9f9a8839 expected csum 0x9f1a8839 mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 34, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 35, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2716147712 csum 0x8db51b1a expected csum 0x8d351b1a mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 36, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2717736960 csum 0x9f9a8839 expected csum 0x9f1a8839 mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 37, gen 0 Feb 25 02:24:06 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 102622873 off 2717736960 csum 0x9f9a8839 expected csum 0x9f1a8839 mirror 1 Feb 25 02:24:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 38, gen 0 Feb 25 02:25:16 Tower emhttpd: read SMART /dev/sdf Feb 25 02:29:47 Tower crond[1421]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Feb 25 02:29:59 Tower emhttpd: read SMART /dev/sdj Feb 25 02:32:57 Tower kernel: mdcmd (63): set md_write_method 1 Feb 25 02:32:57 Tower kernel: Feb 25 03:10:47 Tower emhttpd: spinning down /dev/sdf Feb 25 03:12:58 Tower kernel: mdcmd (64): set md_write_method 0 Feb 25 03:12:58 Tower kernel: Feb 25 03:18:16 Tower emhttpd: spinning down /dev/sdg
February 25, 20224 yr "Corrupt" being reported on btrfs implies (not necessarily though) a memory issue. Run through a pass or 2 of memtest from the boot menu (if you boot via UEFI, then you'll have to temporarily switch to legacy)
February 26, 20224 yr This will look for the possible cause of the error, but will not fix the errors already present. You will have to address the existing corruption.
February 26, 20224 yr Author ok found the corrupted files and I deleted them and replaced them.. errors gone now.. Also I did a memtest ran it over night no errors.. I believe a power failure I had other day caused the corruption. I'll see if it happens again.. Thanks for the help..
February 27, 20224 yr Community Expert 18 hours ago, Spydawg said: I believe a power failure I had other day caused the corruption. Very unlikely a power failure would cause checksum errors, recommend monitoring the pool so you're notified if more corruption is found.
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.