uas error with external USB3 BluRay drive

bmentink · 2017-01-05 20:11:59

Hi Guys,

I am getting the following error when attaching the drive:

[153046.188077] usb 2-3: new high-speed USB device number 23 using ehci-pci
[153046.340285] usbcore: registered new interface driver usb-storage
[153046.348593] scsi host4: uas
[153046.348736] usbcore: registered new interface driver uas
[153046.352508] scsi 4:0:0:0: tag#0 data cmplt err -75 uas-tag 1 inflight: CMD 
[153046.352511] scsi 4:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
[153068.851424] scsi 4:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD 
[153068.851429] scsi 4:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
[153068.851451] scsi host4: uas_eh_bus_reset_handler start
[153068.964743] usb 2-3: reset high-speed USB device number 23 using ehci-pci
[153074.284766] usb 2-3: device descriptor read/64, error -110
[153089.861401] usb 2-3: device descriptor read/64, error -110
[153090.081409] usb 2-3: reset high-speed USB device number 23 using ehci-pci
[153095.408064] usb 2-3: device descriptor read/64, error -110

lsmod

Bus 002 Device 024: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge

Any suggestions on how to resolve this? I am using kernel 4.8.13-1-ARCH

Last edited by bmentink (2017-01-05 20:16:14)

R00KIE · 2017-01-05 23:05:09

It's not a solution but you can workaround the problem by disabling uas for that usb device, see https://bbs.archlinux.org/viewtopic.php?id=183190

If that problem still stands when kernel 4.9.1 hits the stable repos you most probably want to report the problem upstream.

bmentink · 2017-01-05 23:37:57

R00KIE wrote:

It's not a solution but you can workaround the problem by disabling uas for that usb device, see https://bbs.archlinux.org/viewtopic.php?id=183190
If that problem still stands when kernel 4.9.1 hits the stable repos you most probably want to report the problem upstream.

Thanks, I followed that guide and now dmesg shows:

[  135.830050] usb 2-1: new high-speed USB device number 5 using ehci-pci
[  135.969495] usb 2-1: UAS is blacklisted for this device, using usb-storage instead
[  135.969500] usb-storage 2-1:1.0: USB Mass Storage device detected
[  135.974030] usb-storage 2-1:1.0: Quirks match for vid 174c pid 55aa: c00000
[  135.974063] scsi host4: usb-storage 2-1:1.0
[  136.990160] scsi host4: scsi scan: INQUIRY result too short (5), using 36
[  136.990168] scsi 4:0:0:0: Direct-Access                                    PQ: 0 ANSI: 0
[  168.713435] usb 2-1: reset high-speed USB device number 5 using ehci-pci
[  174.033390] usb 2-1: device descriptor read/64, error -110
[  189.606718] usb 2-1: device descriptor read/64, error -110
[  189.826689] usb 2-1: reset high-speed USB device number 5 using ehci-pci
[  195.153374] usb 2-1: device descriptor read/64, error -110
[  210.726677] usb 2-1: device descriptor read/64, error -110
[  210.946693] usb 2-1: reset high-speed USB device number 5 using ehci-pci
[  221.700027] usb 2-1: device not accepting address 5, error -110
[  221.813369] usb 2-1: reset high-speed USB device number 5 using ehci-pci
[  232.366743] usb 2-1: device not accepting address 5, error -110
[  232.366832] usb 2-1: USB disconnect, device number 5
[  232.380151] sd 4:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=0x00
[  232.380156] sd 4:0:0:0: [sdb] Sense not available.
[  232.380174] sd 4:0:0:0: [sdb] Write Protect is off
[  232.380177] sd 4:0:0:0: [sdb] Mode Sense: 00 00 00 00
[  232.380201] sd 4:0:0:0: [sdb] Asking for cache data failed
[  232.380207] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  232.380533] sd 4:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=0x00
[  232.380536] sd 4:0:0:0: [sdb] Sense not available.
[  232.380566] sd 4:0:0:0: [sdb] Attached SCSI disk
[  232.533362] usb 2-1: new high-speed USB device number 6 using ehci-pci
[  237.820037] usb 2-1: device descriptor read/64, error -110
[  253.393422] usb 2-1: device descriptor read/64, error -110
[  253.613365] usb 2-1: new high-speed USB device number 7 using ehci-pci
[  258.943418] usb 2-1: device descriptor read/64, error -110
[  274.516726] usb 2-1: device descriptor read/64, error -110
[  274.736689] usb 2-1: new high-speed USB device number 8 using ehci-pci
[  285.486690] usb 2-1: device not accepting address 8, error -110
[  285.600062] usb 2-1: new high-speed USB device number 9 using ehci-pci
[  296.153358] usb 2-1: device not accepting address 9, error -110
[  296.153400] usb usb2-port1: unable to enumerate USB device
[  296.620045] usb 6-1: new full-speed USB device number 3 using uhci_hcd
[  301.820050] usb 6-1: device descriptor read/64, error -110
[  317.393407] usb 6-1: device descriptor read/64, error -110
[  317.613408] usb 6-1: new full-speed USB device number 4 using uhci_hcd
[  322.940077] usb 6-1: device descriptor read/64, error -110

But still no /dev/srx device ...

Last edited by bmentink (2017-01-05 23:39:14)

bmentink · 2017-01-07 00:49:51

R00KIE wrote:

If that problem still stands when kernel 4.9.1 hits the stable repos you most probably want to report the problem upstream.

How do I do that?

R00KIE · 2017-01-07 01:14:36

For reporting the bug you need an account in the kernel bugzilla[1]. Linux 4.9.1 hasn't been released by upstream yet but 4.9 is already in [testing] if you feel like giving the testing repo a try. Usually only kernel X.Y.1 is released to the stable repos as to give the maintainers time to catch and look for fixes to newly introduced problems, that is why I said wait until 4.9.1 gets to the stable repos.

You could also try compiling the linux-git from the AUR[2] and see if that works, if you intend to report the bug upstream I suppose somewhere along the line you will be asked to try if the problem has been solved in the current git version.

[1] https://bugzilla.kernel.org/
[2] https://aur.archlinux.org/packages/linux-git

Edit:
It seems linux 4.9.1 was just released[3] so it shouldn't take too long until it shows up in [core].

[3] https://lwn.net/Articles/710866/

Last edited by R00KIE (2017-01-07 01:37:15)

MrPeacock · 2017-01-25 18:37:02

Hi Rookie,

same problem here

Jan 25 19:24:44 server partitionmanager[865]: "Scanning devices..."
Jan 25 19:24:44 server partitionmanager[865]: "Device found: ATA TOSHIBA-TR150"
Jan 25 19:24:44 server partitionmanager[865]: getting bad sectors failed for  "/dev/sda" :  No such file or directory
Jan 25 19:24:45 server partitionmanager[865]: "Device found: ST1500DL 003-9VT16L"
Jan 25 19:24:45 server partitionmanager[865]: "Device found: Intenso External USB 3.0"
Jan 25 19:24:45 server partitionmanager[865]: getting smart status failed for  "/dev/sdc" :  Operation not supported
Jan 25 19:24:45 server partitionmanager[865]: "Scan finished."
Jan 25 19:25:09 server konsole[727]: Attempted to re-run an already running session.
Jan 25 19:25:12 server su[1105]: (to root) sascha on pts/1
Jan 25 19:25:12 server su[1105]: pam_unix(su:session): session opened for user root by sascha(uid=1000)
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#6 CDB: opcode=0x2a 2a 00 0d 78 09 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#25 uas_eh_abort_handler 0 uas-tag 26 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#25 CDB: opcode=0x2a 2a 00 0d 78 09 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#8 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#8 CDB: opcode=0x2a 2a 00 0d 78 08 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#12 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#12 CDB: opcode=0x2a 2a 00 0d 78 08 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#9 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#9 CDB: opcode=0x2a 2a 00 0d 70 27 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#26 uas_eh_abort_handler 0 uas-tag 27 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#26 CDB: opcode=0x2a 2a 00 0d 70 27 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#20 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#20 CDB: opcode=0x2a 2a 00 0d 70 26 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#14 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#14 CDB: opcode=0x2a 2a 00 0d 70 26 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#23 uas_eh_abort_handler 0 uas-tag 24 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#23 CDB: opcode=0x2a 2a 00 0d 70 25 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#17 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#17 CDB: opcode=0x2a 2a 00 0d 70 25 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#1 CDB: opcode=0x2a 2a 00 0d 70 24 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#22 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#22 CDB: opcode=0x2a 2a 00 0d 70 24 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#18 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#18 CDB: opcode=0x2a 2a 00 0d 70 23 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#11 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#11 CDB: opcode=0x2a 2a 00 0d 70 23 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#15 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#15 CDB: opcode=0x2a 2a 00 0d 70 22 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#4 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#4 CDB: opcode=0x2a 2a 00 0d 70 22 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#13 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#13 CDB: opcode=0x2a 2a 00 0d 70 21 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#16 CDB: opcode=0x2a 2a 00 0d 70 21 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#10 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#10 CDB: opcode=0x2a 2a 00 0d 70 20 a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#21 uas_eh_abort_handler 0 uas-tag 22 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#21 CDB: opcode=0x2a 2a 00 0d 70 20 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#0 CDB: opcode=0x2a 2a 00 0d 70 1f a0 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#19 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#19 CDB: opcode=0x2a 2a 00 0d 70 1f 20 00 00 80 00
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT 
Jan 25 19:27:35 server kernel: sd 7:0:0:0: [sdc] tag#2 CDB: opcode=0x2a 2a 00 0d 70 1e a0 00 00 80 00
Jan 25 19:27:42 server kernel: sd 7:0:0:0: [sdc] tag#24 uas_eh_abort_handler 0 uas-tag 25 inflight: CMD OUT 
Jan 25 19:27:42 server kernel: sd 7:0:0:0: [sdc] tag#24 CDB: opcode=0x2a 2a 00 0d 70 1e 20 00 00 80 00
Jan 25 19:27:44 server kernel: sd 7:0:0:0: [sdc] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT 
Jan 25 19:27:44 server kernel: sd 7:0:0:0: [sdc] tag#5 CDB: opcode=0x2a 2a 00 0d 70 1d a0 00 00 80 00
Jan 25 19:27:44 server kernel: sd 7:0:0:0: [sdc] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT 
Jan 25 19:27:44 server kernel: sd 7:0:0:0: [sdc] tag#3 CDB: opcode=0x2a 2a 00 0d 70 1d 20 00 00 80 00
Jan 25 19:27:44 server kernel: sd 7:0:0:0: [sdc] tag#7 uas_eh_abort_handler 0 uas-tag 8 inflight: 
Jan 25 19:27:44 server kernel: sd 7:0:0:0: [sdc] tag#7 CDB: opcode=0x2a 2a 00 0d 70 1c a0 00 00 80 00
Jan 25 19:27:44 server kernel: scsi host7: uas_eh_bus_reset_handler start
Jan 25 19:27:48 server kernel: usb 4-1: reset SuperSpeed USB device number 3 using xhci_hcd
Jan 25 19:27:48 server kernel: scsi host7: uas_eh_bus_reset_handler success
Jan 25 19:27:48 server kernel: sd 7:0:0:0: [sdc] tag#7 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD 
Jan 25 19:27:48 server kernel: sd 7:0:0:0: [sdc] tag#7 CDB: opcode=0x0 00 00 00 00 00 00
Jan 25 19:27:49 server kernel: scsi host7: uas_eh_bus_reset_handler start
Jan 25 19:27:51 server kernel: xhci_hcd 0000:01:00.0: Timeout while waiting for setup device command
Jan 25 19:27:56 server kernel: xhci_hcd 0000:01:00.0: Timeout while waiting for setup device command
Jan 25 19:27:56 server kernel: usb 4-1: device not accepting address 3, error -62
Jan 25 19:28:01 server kernel: xhci_hcd 0000:01:00.0: Timeout while waiting for setup device command
Jan 25 19:28:07 server kernel: xhci_hcd 0000:01:00.0: Timeout while waiting for setup device command
Jan 25 19:28:08 server kernel: usb 4-1: device not accepting address 3, error -62
Jan 25 19:28:12 server kernel: xhci_hcd 0000:01:00.0: Timeout while waiting for setup device command
Jan 25 19:28:18 server kernel: xhci_hcd 0000:01:00.0: Timeout while waiting for setup device command
Jan 25 19:28:20 server kernel: usb 4-1: device not accepting address 3, error -62
Jan 25 19:28:23 server kernel: xhci_hcd 0000:01:00.0: Timeout while waiting for setup device command

getting kernel crash after a few seconds when formating an external disk

Bus 004 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge

using latest kernel from testing repository. it seem UAS has still some problems.

regards
S

bmentink · 2017-01-25 18:57:09

R00KIE wrote:

It seems linux 4.9.1 was just released[3] so it shouldn't take too long until it shows up in [core].

It seems Arch is not so bleeding edge after all, Linus has already announced 4.10, but 4.9.1 still hasn't showed up in the Arch repos .. latest is 4.8.13-1

@MrPeacock - What kernel version did you test?

Last edited by bmentink (2017-01-25 19:01:51)

MrPeacock · 2017-01-25 20:30:45

Hi bmentink,

i'm using kernel 4.9.5 in testing repo. For now i've plugged it into a USB2 port and now it finaly formats successful the harddisc.

regards
S

R00KIE · 2017-01-27 11:20:24

bmentink wrote:

R00KIE wrote:
It seems linux 4.9.1 was just released[3] so it shouldn't take too long until it shows up in [core].
It seems Arch is not so bleeding edge after all, Linus has already announced 4.10, but 4.9.1 still hasn't showed up in the Arch repos .. latest is 4.8.13-1

Usually it does show up quickly, however this time up until 4.9.6 there were lots of machines that would not boot with 4.9.x, I suppose you don't want that. You could also enable testing and get the latest bleeding edge.

bmentink · 2017-01-29 19:57:52

Tried testing 4.9.6-1 ... still does not work, same errors ..

R00KIE · 2017-02-01 21:22:09

bmentink wrote:

Tried testing 4.9.6-1 ... still does not work, same errors ..

Try compiling the latest kernel git version and see if it works, if not report the bug upstream[1].

[1] https://bugzilla.kernel.org/

bmentink · 2017-02-01 21:49:44

R00KIE wrote:

bmentink wrote:
Tried testing 4.9.6-1 ... still does not work, same errors ..
Try compiling the latest kernel git version and see if it works, if not report the bug upstream[1].
[1] https://bugzilla.kernel.org/

... a 2G download at 50kB/s .... it's going to take forever. I don't know why the source repo is so slow at the moment ...
(using AUR and linux-git)

Last edited by bmentink (2017-02-01 21:50:46)

R00KIE · 2017-02-02 15:17:55

For me it usually saturates my connection, there may be some problem server side.

bmentink · 2017-02-23 19:41:10

I have upgraded to the latest released kernel 4.9.11-1ARCH ... still same error:

   40.814521] usb 2-1.1: reset high-speed USB device number 3 using ehci-pci
[  233.879066] usb 2-1.2.4: new high-speed USB device number 7 using ehci-pci
[  234.070646] usbcore: registered new interface driver usb-storage
[  234.072641] scsi host6: uas
[  234.072745] usbcore: registered new interface driver uas
[  234.073204] scsi 6:0:0:0: tag#0 data cmplt err -75 uas-tag 1 inflight: CMD 
[  234.073208] scsi 6:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
[  255.985712] scsi 6:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD 
[  255.985717] scsi 6:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
[  255.985762] scsi host6: uas_eh_bus_reset_handler start
[  256.062409] usb 2-1.2.4: reset high-speed USB device number 7 using ehci-pci
[  261.169030] usb 2-1.2.4: device descriptor read/64, error -110
[  276.742206] usb 2-1.2.4: device descriptor read/64, error -110
[  276.922193] usb 2-1.2.4: reset high-speed USB device number 7 using ehci-pci
[  282.075476] usb 2-1.2.4: device descriptor read/64, error -110
[  297.648562] usb 2-1.2.4: device descriptor read/64, error -110
[  297.828589] usb 2-1.2.4: reset high-speed USB device number 7 using ehci-pci

R00KIE · 2017-02-24 00:38:31

bmentink wrote:

I have upgraded to the latest released kernel 4.9.11-1ARCH ... still same error:

Have you reported the problem upstream?

bmentink · 2017-02-24 01:26:49

R00KIE wrote:

bmentink wrote:
I have upgraded to the latest released kernel 4.9.11-1ARCH ... still same error:
Have you reported the problem upstream?

Just have, I was waiting for kernel > 4.9.10
Bug report: here

Last edited by bmentink (2017-02-24 19:15:35)

R00KIE · 2017-02-24 14:31:32

Could you edit your last post and add the link to the bug report? Just in case someone else has the same problem or similar and wants to follow or join the debugging effort in the upstream bug.

txus · 2017-03-09 19:56:50

Same error here with an HDD via SATA to USB3 adapter (a case). Thanks for the bug report.

Arch Linux

#1 2017-01-05 20:11:59

uas error with external USB3 BluRay drive

#2 2017-01-05 23:05:09

Re: uas error with external USB3 BluRay drive

#3 2017-01-05 23:37:57

Re: uas error with external USB3 BluRay drive

#4 2017-01-07 00:49:51

Re: uas error with external USB3 BluRay drive

#5 2017-01-07 01:14:36

Re: uas error with external USB3 BluRay drive

#6 2017-01-25 18:37:02

Re: uas error with external USB3 BluRay drive

#7 2017-01-25 18:57:09

Re: uas error with external USB3 BluRay drive

#8 2017-01-25 20:30:45

Re: uas error with external USB3 BluRay drive

#9 2017-01-27 11:20:24

Re: uas error with external USB3 BluRay drive

#10 2017-01-29 19:57:52

Re: uas error with external USB3 BluRay drive

#11 2017-02-01 21:22:09

Re: uas error with external USB3 BluRay drive

#12 2017-02-01 21:49:44

Re: uas error with external USB3 BluRay drive

#13 2017-02-02 15:17:55

Re: uas error with external USB3 BluRay drive

#14 2017-02-23 19:41:10

Re: uas error with external USB3 BluRay drive

#15 2017-02-24 00:38:31

Re: uas error with external USB3 BluRay drive

#16 2017-02-24 01:26:49

Re: uas error with external USB3 BluRay drive

#17 2017-02-24 14:31:32

Re: uas error with external USB3 BluRay drive

#18 2017-03-09 19:56:50

Re: uas error with external USB3 BluRay drive

Board footer