Hello all. So far I've been very happy with how unRAID has been working, but I've been getting BTRFS errors on and off, but now it's getting a bit ridiculous. 

Sep 5 10:47:15 Asgard kernel: BTRFS warning (device sdi1): lost page write due to IO error on /dev/sdi1
Sep 5 10:47:24 Asgard kernel: btrfs_dev_stat_print_on_error: 28 callbacks suppressed
Sep 5 10:47:24 Asgard kernel: BTRFS error (device sdi1): bdev /dev/sdi1 errs: wr 44507142, rd 67725762, flush 3841, corrupt 350940, gen 1941

This goes on and on and on... and then I started getting call trace errors as well... which should be in the diagnostics I'm posting. Can anyone take a look and give me somewhere to start?

Running all this on a Ryzen 5 1600, AsRock Fatality AB350 Gaming K4 motherboard, 32 GB of RAM, and a whole bunch of hard drives, and a couple SSDs for the cache pool.

 

Thank you!

asgard-diagnostics-20170905-1041.zip

One of your cache devices

Sep  4 14:17:07 Asgard kernel: ata12.00: ATA-10: Crucial_CT275MX300SSD1,         171516B3383A

dropped offline
 

Quote

Sep  5 00:01:55 Asgard kernel: ata12.00: failed command: WRITE FPDMA QUEUED
Sep  5 00:01:55 Asgard kernel: ata12.00: cmd 61/20:a8:00:da:ae/00:00:09:00:00/40 tag 21 ncq dma 16384 out
Sep  5 00:01:55 Asgard kernel:         res 40/00:6c:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
Sep  5 00:01:55 Asgard kernel: ata12.00: status: { DRDY }
Sep  5 00:01:55 Asgard kernel: ata12: hard resetting link
Sep  5 00:02:05 Asgard kernel: ata12: softreset failed (1st FIS failed)
Sep  5 00:02:05 Asgard kernel: ata12: hard resetting link
Sep  5 00:02:15 Asgard kernel: ata12: softreset failed (1st FIS failed)
Sep  5 00:02:15 Asgard kernel: ata12: hard resetting link
Sep  5 00:02:50 Asgard kernel: ata12: softreset failed (1st FIS failed)
Sep  5 00:02:50 Asgard kernel: ata12: limiting SATA link speed to 3.0 Gbps
Sep  5 00:02:50 Asgard kernel: ata12: hard resetting link
Sep  5 00:02:55 Asgard kernel: ata12: softreset failed (1st FIS failed)
Sep  5 00:02:55 Asgard kernel: ata12: reset failed, giving up
Sep  5 00:02:55 Asgard kernel: ata12.00: disabled

 

 

Hence the btrfs errors, it's a hardware problem, most likely cable/connection.

I forgot to mention that you should run a correcting scrub (and make sure all errors were corrected) after the drooped device comes online.

ah... ok thank you! Appreciate the help.