October 24, 20196 yr Hi all, I used to run a Marvell based HBA which constantly stalled, crashed, and gave me BTRFS errors in my cache. I just upgraded to an LSI SAS 9300-4i. Initially all was good. VM related errors are all gone, read/write speeds are increased etc. However occasionally (maybe once every 2 days) I am getting IO errors for one of my SSD drives attached to the HBA: Oct 23 19:08:19 AsQ-NAS kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Oct 23 19:08:19 AsQ-NAS kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x28 28 00 05 fe 18 18 00 05 e0 00 Oct 23 19:08:19 AsQ-NAS kernel: print_req_error: I/O error, dev sdi, sector 100538392 Oct 23 19:08:19 AsQ-NAS kernel: sd 7:0:1:0: [sdi] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Oct 23 19:08:19 AsQ-NAS kernel: sd 7:0:1:0: [sdi] tag#1 Sense Key : 0x2 [current] Oct 23 19:08:19 AsQ-NAS kernel: sd 7:0:1:0: [sdi] tag#1 ASC=0x4 ASCQ=0x2 Oct 23 19:08:19 AsQ-NAS kernel: sd 7:0:1:0: [sdi] tag#1 CDB: opcode=0x28 28 00 05 fe 1d f8 00 09 e0 00 Oct 23 19:08:19 AsQ-NAS kernel: print_req_error: I/O error, dev sdi, sector 100539896 The drive gave no IO errors using the previous marvell controller. I am getting no functionality problems, the drive still works fine and all the data on it seems ok. Some Context: This LSI HBA has 3 SSDs attached to it and that is all. One of the SSDs is my cache drive which is drive sdh, whereas the other 2 ssds (sdi and sdj) are unassigned devices used as shares for my windows 10 vm. I only get errors for drive sdi. The erroring drive is only being used to download a few torrents at a time onto. Some help on where to start troubleshooting this would be much appreciated, to find out whether it is really a drive fail or controller problem etc. Thankyou in advance. Diagnostics attached asq-nas-diagnostics-20191024-1017.zip
October 24, 20196 yr Community Expert Not sure what's causing that but I would try swapping that SSD to one the onboard SATA ports and/or update the LSI firmware, though if it was the latter I would also expect problems with the other Samsung SSD.
October 24, 20196 yr Author 5 hours ago, johnnie.black said: Not sure what's causing that but I would try swapping that SSD to one the onboard SATA ports and/or update the LSI firmware, though if it was the latter I would also expect problems with the other Samsung SSD. Thankyou for the suggestion, I will swap a few drives about and see if the error follows the drive or stays with the same controller/port.
Archived
This topic is now archived and is closed to further replies.