Suggestion for a reliable USB 3.1 Hub?

My 3.1 USB hub just keeps crashing with high activity. My current one is an "Inland 3.1 SuperSpeed" something or other that uses a Type-C to Type-A cable, it's obviously crappy. It's the 3rd one I've tried, the others were a "Orico" and "Xcellon". I've been through 3 in the last 2 weeks and all 3 are pretty much junk considering they all use external power ("wall warts"/transformers).

Aug 17 20:13:54 omv kernel: [774172.008037] scsi host19: uas_eh_device_reset_handler success
Aug 17 20:14:14 omv kernel: [774192.371038] sd 18:0:0:0: [sdf] tag#19 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD OUT 
...
Aug 17 20:14:14 omv kernel: [774192.374161] sd 18:0:0:0: [sdf] tag#7 uas_eh_abort_handler 0 uas-tag 5 inflight: 
Aug 17 20:14:14 omv kernel: [774192.374171] sd 18:0:0:0: [sdf] tag#7 CDB: Write(16) 8a 00 00 00 00 00 83 22 10 28 00 00 01 60 00 00
Aug 17 20:14:14 omv kernel: [774192.387035] scsi host18: uas_eh_device_reset_handler start
Aug 17 20:14:14 omv kernel: [774192.520600] usb 6-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Aug 17 20:14:14 omv kernel: [774192.549667] scsi host18: uas_eh_device_reset_handler success

Any suggestions are welcomed.

Turns out this is the onboard controller.

This did *_NOT_* happen with OMV 1.5 (kralizec)

Good point, no this is on the latest OMV 5.x while copying any file larger than ~100MB. Since almost all files I'm transferring are at least that size, this happens non-stop and the syslog is 400+ pages after just a day.

I'm not sure which driver was used/selected in OMV 1.5 on Debian 7, but it didn't have this problem.

I literally just upgraded because of your heads up :-).

I'll try it after the current Rsync job is finished. Just 600GB, all large tiff files, 74 hours and counting, ~80% done... this is crazy... horrible. If I remember correctly, this didn't even take a day in the old OMV :-/. I wish I would of kept that old image just to see which driver/version it used.

What I haven't done yet is to see if it keeps restarting regardless of transferring files, I'm kind of hoping it does.

The update didn't help, it's still broken. It wound up taking 88 hours to transfer 600GB with rsync to the USB drive in the OMV box. In contrast, I mounted the RAID1 in the OMV box and rsync'd to a USB drive on my PC and it took 23.5 hours to transfer 1.07TB, of which 600GB of that 1.07TB was identical.

Again, this problem didn't exist with OMV 1.5.

Here's what hwinfo lists on the OMV box:

15: PCI 13.2: 0c03 USB Controller (EHCI)
  [Created at pci.386]
  Unique ID: 06bT.jPsMPYxld01
  SysFS ID: /devices/pci0000:00/0000:00:13.2
  SysFS BusID: 0000:00:13.2
  Hardware Class: usb controller
  Model: "ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x4396 "SB7x0/SB8x0/SB9x0 USB EHCI Controller"
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x8389 
  Driver: "ehci-pci"
  Driver Modules: "ehci_pci"
  Memory Range: 0xfe6ff400-0xfe6ff4ff (rw,non-prefetchable)
  IRQ: 19 (71 events)
  Module Alias: "pci:v00001002d00004396sv00001043sd00008389bc0Csc03i20"
  Driver Info #0:
    Driver Status: ehci-hcd is active
    Driver Activation Cmd: "modprobe ehci-hcd"
  Driver Info #1:
    Driver Status: ehci_pci is active
    Driver Activation Cmd: "modprobe ehci_pci"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Strangely, the chipset is different but the driver is the same on PC, where USB is working fine:

23: PCI 1a.0: 0c03 USB Controller (EHCI)
  [Created at pci.386]
  Unique ID: pwJ7.qHlUcQHlAr4
  SysFS ID: /devices/pci0000:00/0000:00:1a.0
  SysFS BusID: 0000:00:1a.0
  Hardware Class: usb controller
  Model: "Intel 7 Series/C216 Chipset Family USB Enhanced Host Controller #2"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x1e2d "7 Series/C216 Chipset Family USB Enhanced Host Controller #2"
  SubVendor: pci 0x1849 "ASRock Incorporation"
  SubDevice: pci 0x1e2d "Motherboard"
  Revision: 0x04
  Driver: "ehci-pci"
  Memory Range: 0xf7818000-0xf78183ff (rw,non-prefetchable)
  IRQ: 16 (48550551 events)
  Module Alias: "pci:v00008086d00001E2Dsv00001849sd00001E2Dbc0Csc03i20"
  Driver Info #0:
    Driver Status: ehci-hcd is not active
    Driver Activation Cmd: "modprobe ehci-hcd"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

This very well could be a driver bug with that old ATI SBxxx chipset, but which driver was used for it in OMV 1.5?