Hello I am trying to follow up on the original thread, opened on this issue by Christoph Gohle May 2017 (same email subject) I confirm that the same issue is still present on kernel 4.14.15 (Mainline build for Ubuntu xenial, amd64) My enclosure is an Orico 9558RU3, using JMS567 USB 3.0 to SATA bridge together with JMB394 multiplexer with RAID As soon as more than one HD in inserted in the enclosure, when parallel write operation are send to the HDs, you start to get immediately CMD error on UAS driver, after a while the USB gets in an inconsistent status and you are forced to reset. Jan 27 08:59:53 Menionubuntu kernel: [ 750.564095] sd 0:0:0:1: [sdb] tag#22 CDB: Write(10) 2a 00 00 5e fb 10 00 04 00 00 Jan 27 08:59:53 Menionubuntu kernel: [ 750.567579] sd 0:0:0:1: [sdb] tag#17 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD OUT Jan 27 08:59:53 Menionubuntu kernel: [ 750.567604] sd 0:0:0:1: [sdb] tag#17 CDB: Write(10) 2a 00 00 5e f7 10 00 04 00 00 Jan 27 08:59:53 Menionubuntu kernel: [ 750.571280] sd 0:0:0:1: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD OUT Jan 27 08:59:53 Menionubuntu kernel: [ 750.571299] sd 0:0:0:1: [sdb] tag#16 CDB: Write(10) 2a 00 00 5e f3 10 00 04 00 00 Jan 27 08:59:53 Menionubuntu kernel: [ 750.575292] sd 0:0:0:1: [sdb] tag#15 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT Jan 27 08:59:53 Menionubuntu kernel: [ 750.575304] sd 0:0:0:1: [sdb] tag#15 CDB: Write(10) 2a 00 00 5e ef 10 00 04 00 00 With BTFS the things go even worst: Jan 26 18:46:01 Menionubuntu kernel: [22961.078609] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 26 18:46:02 Menionubuntu kernel: [22961.160317] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Jan 26 18:46:02 Menionubuntu kernel: [22961.160378] sd 0:0:0:0: [sda] tag#0 Sense Key : Aborted Command [current] Jan 26 18:46:02 Menionubuntu kernel: [22961.160523] sd 0:0:0:0: [sda] tag#0 Add. Sense: No additional sense information Jan 26 18:46:02 Menionubuntu kernel: [22961.160544] sd 0:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Jan 26 18:46:02 Menionubuntu kernel: [22961.160558] print_req_error: I/O error, dev sda, sector 0 Jan 26 18:46:02 Menionubuntu kernel: [22961.160597] Buffer I/O error on dev sda, logical block 0, async page read Jan 26 18:46:02 Menionubuntu kernel: [22961.244469] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Jan 26 18:46:02 Menionubuntu kernel: [22961.244539] sd 0:0:0:0: [sda] tag#0 Sense Key : Aborted Command [current] Jan 26 18:46:02 Menionubuntu kernel: [22961.244556] sd 0:0:0:0: [sda] tag#0 Add. Sense: No additional sense information Jan 26 18:46:02 Menionubuntu kernel: [22961.244577] sd 0:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Jan 26 18:46:02 Menionubuntu kernel: [22961.244590] print_req_error: I/O error, dev sda, sector 0 Putting in UAS blacklist the device so running old BOT mode is a valid workaround, the same enclosure with the same HDs run for days with no USB error. Due to the fact that I am running JBOD on BTRFS, I really need to run in BOT mode, but I can try to provide some logs, if anyone is willing to pick up the issue. Bye -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
