So I discovered today that my docker containers won't load and thought that I needed to delete/recreate the image and all would be ok. But deleting the image from settings and then on bash didn't work. I then went to take a look at my cache pool and that's when things looked iffy. Here's the cache disk log:

Quote

Jan 16 04:42:17 HK-HomeLab kernel: sd 14:0:2:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 16 04:42:17 HK-HomeLab kernel: sd 14:0:2:0: [sdi] tag#0 Sense Key : 0x2 [current]
Jan 16 04:42:17 HK-HomeLab kernel: sd 14:0:2:0: [sdi] tag#0 ASC=0x4 ASCQ=0x0
Jan 16 04:42:17 HK-HomeLab kernel: sd 14:0:2:0: [sdi] tag#0 CDB: opcode=0x28 28 00 07 bb 73 80 00 00 08 00
Jan 16 04:42:21 HK-HomeLab kernel: sd 14:0:2:0: [sdi] Synchronizing SCSI cache
Jan 16 04:42:21 HK-HomeLab kernel: sd 14:0:2:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Jan 16 04:42:22 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 456160, flush 1, corrupt 0, gen 0
Jan 16 04:42:22 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 456161, flush 1, corrupt 0, gen 0
Jan 16 04:42:22 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 456162, flush 1, corrupt 0, gen 0
Jan 16 04:42:22 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 456163, flush 1, corrupt 0, gen 0
Jan 16 04:42:22 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 456164, flush 1, corrupt 0, gen 0
Jan 16 04:42:27 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 601003, flush 1, corrupt 0, gen 0
Jan 16 04:42:27 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 601004, flush 1, corrupt 0, gen 0
Jan 16 04:42:27 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 601005, flush 1, corrupt 0, gen 0
Jan 16 04:42:27 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 601006, flush 1, corrupt 0, gen 0
Jan 16 04:42:27 HK-HomeLab kernel: BTRFS error (device dm-4): bdev /dev/mapper/sdi1 errs: wr 446, rd 601007, flush 1, corrupt 0, gen 0

Then strange thing is that I have 18,446,744,073,703,520,256 reads and 18,446,744,073,702,512,640 writes. The SSD temperature is no longer displayed and replaced with a "*". But unRAID tells me that the device is in normal operation and active. Something looks seriously wrong and I seem to be only do read-only on the files located in the cache. Any suggestions on my next step? Many thanks!

I've had this happen to me twice now.  I've seen suggestions that it could be as simple as a bad SATA cable, but running in an R710 makes it difficult for me to test that at this time. (proprietary SATA cable and SSD sled for the optical bay)  Your drive is readable, create a space on the array, and copy everything over as a backup.  Reboot.  I found that typically a reboot reset the error state and everything was happy.  The first time I swapped the drive and later learned that there was no need as the drive was still good.  Thankfully I had access to a spare.

 

---aaaandd mine just hosed up again too.

Edited January 19, 20188 yr by NeoMatrixJR

22 hours ago, ipreferpie said:

Any suggestions on my next step? Many thanks!

Could swear I replied to this thread earlier, please post your diagnostics: Tools -> Diagnostics