I recently moved my machine around and I have since started to get errors thrown in syslog for the two SSDs which I have hosting the files for my docker containers and such, and it appears to have been causing some issues since the move. Nothing before the move afaik, so I am really confused. I have tried them on two different cables on the HBA, no joy, so either the HBA is borked (which I doubt as the other drives appear fine), the drives themselves are bad, or I have another issue that is masquerading as an issue with the SSDs.

Hardware in question:
HBA - LSI 9400-16i (running in a 4x wired 16x slot, appears the be running the latest firmware as far as I can tell)
SSDs - Samsung 860 Evo 500GB

Error (this shows one drive but I have also seen a similar error on another drive):

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: attempting task abort!scmd(0x000000000f47542d), outstanding for 30212 ms & timeout 30000 ms

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: [sdf] tag#299 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00

Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: handle(0x002f), sas_address(0x300605b010b23967), phy(7)

Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure logical id(0x300605b010113960), slot(11)

Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure level(0x0000), connector name( C2 )

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: task abort: SUCCESS scmd(0x000000000f47542d)

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: attempting task abort!scmd(0x000000002ece6e8d), outstanding for 30242 ms & timeout 30000 ms

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: [sdf] tag#297 CDB: opcode=0x2a 2a 08 00 00 08 80 00 00 08 00

Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: handle(0x002f), sas_address(0x300605b010b23967), phy(7)

Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure logical id(0x300605b010113960), slot(11)

Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure level(0x0000), connector name( C2 )

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: No reference found at driver, assuming scmd(0x000000002ece6e8d) might have completed

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: task abort: SUCCESS scmd(0x000000002ece6e8d)

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: attempting task abort!scmd(0x00000000fbaff48a), outstanding for 30186 ms & timeout 30000 ms

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: [sdf] tag#292 CDB: opcode=0x2a 2a 00 09 14 d7 40 00 00 b8 00

Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: handle(0x002f), sas_address(0x300605b010b23967), phy(7)

Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure logical id(0x300605b010113960), slot(11)

Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure level(0x0000), connector name( C2 )

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: No reference found at driver, assuming scmd(0x00000000fbaff48a) might have completed

Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: task abort: SUCCESS scmd(0x00000000fbaff48a)

Dec 13 20:32:51 lil-NAS-x kernel: sd 9:0:5:0: Power-on or device reset occurred

Really appreciate anybodies suggestions regarding this.

Could just be a compatibility issue; if possible, it may be preferable to use onboard SATA for those