Lastnight I upgraded from unraid 6.2.4 to 6.3.2.  The upgrade went smoothly and everything appeared to work fine.  

 

I then proceeded to try pass through a new USB card and accidentally passed through the USB bus with the unraid usb.  The system lost access to the USB drive and started throwing error messages.  I rebooted to server and was able to re-enable the VM manager but I no longer had my cache drives displayed.  The unraid server showed one of the two drives in my cache pool missing and the syslog made reference to sata failures.  After replacing the SATA cables, power cables and moving the two cache drives to different SATA ports am finally able to get both drives to show up in the Unraid GUI.  However, the drives go into readonly mode. 

 

Jun 19 00:05:47 BriansTower kernel: sas: sas_scsi_find_task: task 0xffff88203662d700 is done
Jun 19 00:05:47 BriansTower kernel: sas: sas_eh_handle_sas_errors: task 0xffff88203662d700 is done
Jun 19 00:05:47 BriansTower kernel: sas: ata8: end_device-4:1: cmd error handler
Jun 19 00:05:47 BriansTower kernel: sas: ata7: end_device-4:0: dev error handler
Jun 19 00:05:47 BriansTower kernel: sas: ata8: end_device-4:1: dev error handler
Jun 19 00:05:47 BriansTower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 19 00:05:47 BriansTower kernel: ata8.00: failed command: WRITE DMA EXT
Jun 19 00:05:47 BriansTower kernel: ata8.00: cmd 35/00:20:e0:42:aa/00:00:31:00:00/e0 tag 5 dma 16384 out
Jun 19 00:05:47 BriansTower kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 19 00:05:47 BriansTower kernel: ata8.00: status: { DRDY }
Jun 19 00:05:47 BriansTower kernel: sas: ata9: end_device-4:2: dev error handler
Jun 19 00:05:47 BriansTower kernel: ata8: hard resetting link
Jun 19 00:05:48 BriansTower kernel: ata8.00: configured for UDMA/33
Jun 19 00:05:48 BriansTower kernel: sd 4:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jun 19 00:05:48 BriansTower kernel: sd 4:0:1:0: [sdi] tag#0 Sense Key : 0x5 [current]
Jun 19 00:05:48 BriansTower kernel: sd 4:0:1:0: [sdi] tag#0 ASC=0x21 ASCQ=0x4
Jun 19 00:05:48 BriansTower kernel: sd 4:0:1:0: [sdi] tag#0 CDB: opcode=0x2a 2a 00 31 aa 42 e0 00 00 20 00
Jun 19 00:05:48 BriansTower kernel: blk_update_request: I/O error, dev sdi, sector 833241824
Jun 19 00:05:48 BriansTower kernel: BTRFS error (device sdi1): bdev /dev/sdi1 errs: wr 233, rd 0, flush 0, corrupt 0, gen 0
Jun 19 00:05:48 BriansTower kernel: ata8: EH complete
Jun 19 00:05:48 BriansTower kernel: BTRFS: error (device sdi1) in btrfs_commit_transaction:2227: errno=-5 IO failure (Error while writing out transact
ion)
Jun 19 00:05:48 BriansTower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1
Jun 19 00:05:48 BriansTower kernel: BTRFS info (device sdi1): forced readonly
Jun 19 00:05:48 BriansTower kernel: BTRFS warning (device sdi1): Skipping commit of aborted transaction.

 Any ideas how to proceed?  

brianstower-diagnostics-20170619-0007.zip

There are write errors on one of the cache devices (cache2), first thing you need is to fix those, check/replace cables.

 

There are many prior errors also on cache1, replace those cables also to rule them out.

 

Then reset the errors by typing:

 

btrfs dev stats -z /mnt/cache

 

and run a scrub, if it keeps going read only best to backup data and reformat.

 

 

Edited June 19, 20179 yr by johnnie.black