USB 3.0 problems

Post Reply
obinary
Posts: 8
Joined: Tue Aug 04, 2020 7:58 am
languages_spoken: english
ODROIDs: ODROID-H2+
Has thanked: 0
Been thanked: 2 times
Contact:

USB 3.0 problems

Post by obinary »

Hi,

My Odroid H2+ has two ORICO Dual Bay connected to USB 3.0 ports. Each Dual Bay has only one SDD.
In the OS, both SSDs are mounted as a RAID 0.

When working with the RAID sometimes the Dual Bay connected to the USB 3.0 on the top randomly gets "disconnected" and his SDD led turns off. After that the RAID becomes inaccessible. It always occurs with the Dual Bay connected to the USB 3.0 on the top but never happens with the one at the bottom.

I have tested with another third bay, same issue.
I have tested with Ubuntu 20.04, same issue.
I have tested with these BIOS: 1.10 and 1.23, same issue.
I have tested with another Odroid H2+, same issue but less frequent.

Anyone having similar issues? Any ideas?

Thanks in advance.


Other notes:
Orico uses JMicron JMS561U controller (300MB/s)

https://www.amazon.es/gp/product/B07X3BTRWP

User avatar
mctom
Posts: 438
Joined: Wed Nov 11, 2020 4:44 am
languages_spoken: english, polish
ODROIDs: N2+, Game Advance, a few XU4
Location: Gdansk, Poland
Has thanked: 48 times
Been thanked: 41 times
Contact:

Re: USB 3.0 problems

Post by mctom »

Hi,
I used to have problems with JMicron adapter on my N2+, see here: viewtopic.php?p=327759#p327759
Anyway, one thing worth trying is to use USB3 extension cable. I can't say how but it did cause far less issues. If that would be the case, then at lest we'll know that's the same problem.

Anything else you got connected to these USB ports?
Anything appearing in dmesg when this happens?
Punk ain't no religious cult, punk means thinking for yourself!

Maintainer of PiStackMon

obinary
Posts: 8
Joined: Tue Aug 04, 2020 7:58 am
languages_spoken: english
ODROIDs: ODROID-H2+
Has thanked: 0
Been thanked: 2 times
Contact:

Re: USB 3.0 problems

Post by obinary »

Hi mctom,
Thanks for replying.

I do not have any USB3 extension cable to test.
No, there is nothing more connected with the USB 3.0 only the dual bays (each in their respective USB 3.0)

I also tried to disable the UAS for these devices, similar issue...
After a while the Dual Bay connected on the top gets unresponsive but, in this case, his SDD led is still blinking.


dmesg shows:
[ 3639.543883] sd 3:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=15s
[ 3639.543894] sd 3:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 11 c4 08 2a 00 00 08 00
[ 3639.543903] blk_update_request: I/O error, dev sdb, sector 298059818 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 0
[ 3639.543915] Buffer I/O error on dev md0, logical block 74448897, lost async page write
[ 3642.165847] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 3644.818595] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 3647.472017] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 3650.125071] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 3652.778222] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 3655.431331] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 3655.449567] sd 3:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=15s
[ 3655.449577] sd 3:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 11 c4 08 42 00 00 08 00
[ 3655.449587] blk_update_request: I/O error, dev sdb, sector 298059842 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 0
[ 3655.449599] Buffer I/O error on dev md0, logical block 74448900, lost async page write

obinary
Posts: 8
Joined: Tue Aug 04, 2020 7:58 am
languages_spoken: english
ODROIDs: ODROID-H2+
Has thanked: 0
Been thanked: 2 times
Contact:

Re: USB 3.0 problems

Post by obinary »

Update:

I have tested with latest Ubuntu 21.04, same issue.

dmesg:
[ 3643.404715] xhci_hcd 0000:00:15.0: ERROR Unknown event condition 10 for slot 4 ep 7 , HC probably busted
[ 3674.855747] sd 3:0:0:0: [sdb] tag#29 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT
[ 3674.855793] sd 3:0:0:0: [sdb] tag#29 CDB: Write(10) 2a 00 06 ac d4 22 00 02 00 00
[ 3674.855977] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.856111] sd 3:0:0:0: [sdb] tag#28 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
[ 3674.856127] sd 3:0:0:0: [sdb] tag#28 CDB: Write(10) 2a 00 06 ac d8 22 00 02 00 00
[ 3674.856167] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.856254] sd 3:0:0:0: [sdb] tag#8 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT
[ 3674.856264] sd 3:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 06 a2 94 22 00 02 00 00
[ 3674.856303] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.856362] sd 3:0:0:0: [sdb] tag#7 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT
[ 3674.856375] sd 3:0:0:0: [sdb] tag#7 CDB: Write(10) 2a 00 06 a2 98 22 00 02 00 00
[ 3674.856411] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.856477] sd 3:0:0:0: [sdb] tag#6 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT
[ 3674.856488] sd 3:0:0:0: [sdb] tag#6 CDB: Write(10) 2a 00 06 a2 9c 22 00 03 20 00
[ 3674.856527] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.856572] sd 3:0:0:0: [sdb] tag#5 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT
[ 3674.856581] sd 3:0:0:0: [sdb] tag#5 CDB: Write(10) 2a 00 06 a2 9a 22 00 02 00 00
[ 3674.856615] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.856655] sd 3:0:0:0: [sdb] tag#4 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT
[ 3674.856664] sd 3:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 06 a2 96 22 00 02 00 00
[ 3674.856696] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.856733] sd 3:0:0:0: [sdb] tag#3 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT
[ 3674.856742] sd 3:0:0:0: [sdb] tag#3 CDB: Write(10) 2a 00 06 a2 92 22 00 02 00 00
[ 3674.856776] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.856824] sd 3:0:0:0: [sdb] tag#2 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT
[ 3674.856837] sd 3:0:0:0: [sdb] tag#2 CDB: Write(10) 2a 00 06 a2 8e 22 00 02 00 00
[ 3674.856873] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.856924] sd 3:0:0:0: [sdb] tag#1 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT
[ 3674.856933] sd 3:0:0:0: [sdb] tag#1 CDB: Write(10) 2a 00 06 ac cc 22 00 02 00 00
[ 3674.856966] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.857001] sd 3:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT
[ 3674.857011] sd 3:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 06 ac d0 22 00 02 00 00
[ 3674.857045] xhci_hcd 0000:00:15.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 3674.883427] scsi host3: uas_eh_device_reset_handler start
[ 3675.011948] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 3675.035210] scsi host3: uas_eh_device_reset_handler success
[ 3711.720679] scsi host3: uas_eh_device_reset_handler start
[ 3711.723322] sd 3:0:0:0: [sdb] tag#0 uas_zap_pending 0 uas-tag 1 inflight: CMD
[ 3711.723338] sd 3:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 06 ac d0 22 00 02 00 00
[ 3711.723348] sd 3:0:0:0: [sdb] tag#1 uas_zap_pending 0 uas-tag 2 inflight: CMD
[ 3711.723355] sd 3:0:0:0: [sdb] tag#1 CDB: Write(10) 2a 00 06 ac cc 22 00 02 00 00
[ 3711.723364] sd 3:0:0:0: [sdb] tag#2 uas_zap_pending 0 uas-tag 3 inflight: CMD
[ 3711.723370] sd 3:0:0:0: [sdb] tag#2 CDB: Write(10) 2a 00 06 a2 8e 22 00 02 00 00
[ 3711.723378] sd 3:0:0:0: [sdb] tag#3 uas_zap_pending 0 uas-tag 4 inflight: CMD
[ 3711.723385] sd 3:0:0:0: [sdb] tag#3 CDB: Write(10) 2a 00 06 a2 92 22 00 02 00 00
[ 3711.723393] sd 3:0:0:0: [sdb] tag#4 uas_zap_pending 0 uas-tag 5 inflight: CMD
[ 3711.723399] sd 3:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 06 a2 96 22 00 02 00 00
[ 3711.723407] sd 3:0:0:0: [sdb] tag#5 uas_zap_pending 0 uas-tag 6 inflight: CMD
[ 3711.723413] sd 3:0:0:0: [sdb] tag#5 CDB: Write(10) 2a 00 06 a2 9a 22 00 02 00 00
[ 3711.723421] sd 3:0:0:0: [sdb] tag#6 uas_zap_pending 0 uas-tag 7 inflight: CMD
[ 3711.723428] sd 3:0:0:0: [sdb] tag#6 CDB: Write(10) 2a 00 06 a2 9c 22 00 03 20 00
[ 3711.723436] sd 3:0:0:0: [sdb] tag#7 uas_zap_pending 0 uas-tag 8 inflight: CMD
[ 3711.723442] sd 3:0:0:0: [sdb] tag#7 CDB: Write(10) 2a 00 06 a2 98 22 00 02 00 00
[ 3711.723450] sd 3:0:0:0: [sdb] tag#9 uas_zap_pending 0 uas-tag 9 inflight: CMD
[ 3711.723457] sd 3:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 06 a2 94 22 00 02 00 00
[ 3711.723465] sd 3:0:0:0: [sdb] tag#10 uas_zap_pending 0 uas-tag 10 inflight: CMD
[ 3711.723472] sd 3:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 06 ac d8 22 00 02 00 00
[ 3711.723480] sd 3:0:0:0: [sdb] tag#11 uas_zap_pending 0 uas-tag 11 inflight: CMD
[ 3711.723486] sd 3:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 06 ac d4 22 00 02 00 00
[ 3711.849166] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 3711.875804] scsi host3: uas_eh_device_reset_handler success
[ 3748.582115] scsi host3: uas_eh_device_reset_handler start
[ 3864.190228] sd 3:0:0:0: [sdb] tag#12 timing out command, waited 180s
[ 3864.190258] sd 3:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_SENSE cmd_age=220s
[ 3864.190269] sd 3:0:0:0: [sdb] tag#12 Sense Key : Hardware Error [current]
[ 3864.190279] sd 3:0:0:0: [sdb] tag#12 Add. Sense: Internal target failure
[ 3864.190288] sd 3:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 06 a2 8e 22 00 02 00 00
[ 3864.190295] blk_update_request: I/O error, dev sdb, sector 111316514 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0
[ 3864.190338] sd 3:0:0:0: [sdb] tag#13 timing out command, waited 180s
[ 3864.190350] sd 3:0:0:0: [sdb] tag#13 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK cmd_age=220s
[ 3864.190358] sd 3:0:0:0: [sdb] tag#13 CDB: Write(10) 2a 00 06 a2 92 22 00 02 00 00
[ 3864.190362] blk_update_request: I/O error, dev sdb, sector 111317538 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0
[ 3864.190390] sd 3:0:0:0: [sdb] tag#14 timing out command, waited 180s
[ 3864.190400] sd 3:0:0:0: [sdb] tag#14 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK cmd_age=220s
[ 3864.190407] sd 3:0:0:0: [sdb] tag#14 CDB: Write(10) 2a 00 06 a2 96 22 00 02 00 00
[ 3864.190412] blk_update_request: I/O error, dev sdb, sector 111318562 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0
[ 3864.190432] sd 3:0:0:0: [sdb] tag#15 timing out command, waited 180s
[ 3864.190442] sd 3:0:0:0: [sdb] tag#15 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK cmd_age=220s
[ 3864.190449] sd 3:0:0:0: [sdb] tag#15 CDB: Write(10) 2a 00 06 a2 9a 22 00 02 00 00
[ 3864.190454] blk_update_request: I/O error, dev sdb, sector 111319586 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0
[ 3864.190474] sd 3:0:0:0: [sdb] tag#16 timing out command, waited 180s
[ 3864.190484] sd 3:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK cmd_age=220s
[ 3864.190491] sd 3:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 06 a2 9c 22 00 03 20 00
[ 3864.190496] blk_update_request: I/O error, dev sdb, sector 111320098 op 0x1:(WRITE) flags 0x0 phys_seg 100 prio class 0
[ 3864.190515] sd 3:0:0:0: [sdb] tag#17 timing out command, waited 180s
[ 3864.190525] sd 3:0:0:0: [sdb] tag#17 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK cmd_age=220s
[ 3864.190532] sd 3:0:0:0: [sdb] tag#17 CDB: Write(10) 2a 00 06 a2 98 22 00 02 00 00
[ 3864.190536] blk_update_request: I/O error, dev sdb, sector 111319074 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0
[ 3864.190556] sd 3:0:0:0: [sdb] tag#18 timing out command, waited 180s
[ 3864.190565] sd 3:0:0:0: [sdb] tag#18 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK cmd_age=220s
[ 3864.190572] sd 3:0:0:0: [sdb] tag#18 CDB: Write(10) 2a 00 06 a2 94 22 00 02 00 00
[ 3864.190577] blk_update_request: I/O error, dev sdb, sector 111318050 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0
[ 3864.190596] sd 3:0:0:0: [sdb] tag#19 timing out command, waited 180s
[ 3864.190605] sd 3:0:0:0: [sdb] tag#19 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK cmd_age=220s
[ 3864.190613] sd 3:0:0:0: [sdb] tag#19 CDB: Write(10) 2a 00 06 ac d4 22 00 02 00 00
[ 3864.190617] blk_update_request: I/O error, dev sdb, sector 111989794 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0
[ 3864.190636] sd 3:0:0:0: [sdb] tag#20 timing out command, waited 180s
[ 3864.190646] sd 3:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK cmd_age=220s
[ 3864.190653] sd 3:0:0:0: [sdb] tag#20 CDB: Write(10) 2a 00 06 ac cc 22 00 02 00 00
[ 3864.190657] blk_update_request: I/O error, dev sdb, sector 111987746 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0
[ 3864.190676] sd 3:0:0:0: [sdb] tag#21 timing out command, waited 180s
[ 3864.190685] sd 3:0:0:0: [sdb] tag#21 FAILED Result: hostbyte=DID_RESET driverbyte=DRIVER_OK cmd_age=220s
[ 3864.190692] sd 3:0:0:0: [sdb] tag#21 CDB: Write(10) 2a 00 06 ac d8 22 00 02 00 00
[ 3864.190697] blk_update_request: I/O error, dev sdb, sector 111990818 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 0
[ 3864.190716] sd 3:0:0:0: [sdb] tag#23 timing out command, waited 180s
[ 3864.190726] EXT4-fs warning (device md0): ext4_end_bio:342: I/O error 10 writing to inode 2884042 starting block 13999080)
[ 3896.026925] sd 3:0:0:0: [sdb] tag#29 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT
[ 3896.026948] sd 3:0:0:0: [sdb] tag#29 CDB: Write(10) 2a 00 06 a8 f4 22 00 01 70 00
[ 3896.027058] sd 3:0:0:0: [sdb] tag#28 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT
[ 3896.027067] sd 3:0:0:0: [sdb] tag#28 CDB: Write(10) 2a 00 06 a8 f0 22 00 01 70 00
[ 3896.027149] sd 3:0:0:0: [sdb] tag#27 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT
[ 3896.027158] sd 3:0:0:0: [sdb] tag#27 CDB: Write(10) 2a 00 06 a8 f8 22 00 01 70 00
[ 3896.027234] sd 3:0:0:0: [sdb] tag#26 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT
[ 3896.027243] sd 3:0:0:0: [sdb] tag#26 CDB: Write(10) 2a 00 06 a8 f9 92 00 02 90 00
[ 3896.027317] sd 3:0:0:0: [sdb] tag#25 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT
[ 3896.027326] sd 3:0:0:0: [sdb] tag#25 CDB: Write(10) 2a 00 06 a8 f5 92 00 02 90 00
[ 3896.027400] sd 3:0:0:0: [sdb] tag#24 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT
[ 3896.027408] sd 3:0:0:0: [sdb] tag#24 CDB: Write(10) 2a 00 06 a8 f1 92 00 02 90 00
[ 3896.027482] sd 3:0:0:0: [sdb] tag#23 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT
[ 3896.027490] sd 3:0:0:0: [sdb] tag#23 CDB: Write(10) 2a 00 06 a8 ed 92 00 02 90 00
[ 3896.027565] sd 3:0:0:0: [sdb] tag#22 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
[ 3896.027574] sd 3:0:0:0: [sdb] tag#22 CDB: Write(10) 2a 00 06 a2 90 22 00 02 00 00
[ 3896.027634] sd 3:0:0:0: [sdb] tag#21 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT
[ 3896.027643] sd 3:0:0:0: [sdb] tag#21 CDB: Write(10) 2a 00 06 a2 8c 22 00 02 00 00
[ 3896.027700] sd 3:0:0:0: [sdb] tag#20 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT
[ 3896.027708] sd 3:0:0:0: [sdb] tag#20 CDB: Write(10) 2a 00 0c 68 8c 22 00 00 28 00
[ 3896.027764] sd 3:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT
[ 3896.027773] sd 3:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 06 a8 ec 22 00 01 70 00
[ 3896.042722] scsi host3: uas_eh_device_reset_handler start
[ 3896.175112] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 3896.197725] scsi host3: uas_eh_device_reset_handler success
Last edited by obinary on Sun Aug 15, 2021 6:16 am, edited 1 time in total.

obinary
Posts: 8
Joined: Tue Aug 04, 2020 7:58 am
languages_spoken: english
ODROIDs: ODROID-H2+
Has thanked: 0
Been thanked: 2 times
Contact:

Re: USB 3.0 problems

Post by obinary »

Update:

Now, tested with Ubuntu 21.04 with UAS disabled.

dmesg:
[ 8534.681099] usb 2-2: Disable of device-initiated U1 failed.
[ 8539.800326] usb 2-2: Disable of device-initiated U2 failed.
[ 8539.928601] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8539.950094] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=10s
[ 8539.950116] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 13 17 90 22 00 08 00 00
[ 8539.950123] blk_update_request: I/O error, dev sdb, sector 320311330 op 0x0:(READ) flags 0x80700 phys_seg 256 prio class 0
[ 8573.217845] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8575.889715] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8578.561408] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8581.225161] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8583.888918] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8586.552636] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8586.573612] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=44s
[ 8586.573631] sd 3:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 76 58 22 00 04 00 00
[ 8586.573638] blk_update_request: I/O error, dev sdb, sector 7755810 op 0x1:(WRITE) flags 0x0 phys_seg 104 prio class 0
[ 8586.573665] EXT4-fs warning (device md0): ext4_end_bio:342: I/O error 10 writing to inode 2883687 starting block 969648)
[ 8586.575159] sd 3:0:0:0: [sdb] Unaligned partial completion (resid=2496, sector_sz=512)
[ 8586.575173] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 13 17 98 22 00 04 00 00
[ 8586.575193] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[ 8586.575201] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 13 17 98 22 00 04 00 00
[ 8586.575206] blk_update_request: I/O error, dev sdb, sector 320313378 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0
[ 8618.269915] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8620.933612] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8623.597373] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8626.261135] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8628.924896] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8631.596707] usb 2-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 8631.617948] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=45s
[ 8631.617969] sd 3:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 0c 72 8e e2 00 00 a8 00
[ 8631.617977] blk_update_request: I/O error, dev sdb, sector 208834274 op 0x1:(WRITE) flags 0x800 phys_seg 21 prio class 0

User avatar
mctom
Posts: 438
Joined: Wed Nov 11, 2020 4:44 am
languages_spoken: english, polish
ODROIDs: N2+, Game Advance, a few XU4
Location: Gdansk, Poland
Has thanked: 48 times
Been thanked: 41 times
Contact:

Re: USB 3.0 problems

Post by mctom »

Looks very familiar. However, my problems were solved by moving to official Ubuntu and not thrashing the hell out of my HDD. I mean, it seems I can reproduce this problem by running badblocks on my HDD, but it never occurs during normal use.
I'm starting to think there might be an actual problem with component layout, after all the top USB port has longer leads to PCB. Moreover, I did report that using a stupid extension cable fully mitigated the problem. For the record, my HDD is also connected to top port, as it never occurred to me the bottom one could be "better". I'll try to test that tomorrow.
Punk ain't no religious cult, punk means thinking for yourself!

Maintainer of PiStackMon

obinary
Posts: 8
Joined: Tue Aug 04, 2020 7:58 am
languages_spoken: english
ODROIDs: ODROID-H2+
Has thanked: 0
Been thanked: 2 times
Contact:

Re: USB 3.0 problems

Post by obinary »

I tried with an USB3 extension cable and that did not solve anything, same issue.

User avatar
odroid
Site Admin
Posts: 38033
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 1999 times
Been thanked: 1206 times
Contact:

Re: USB 3.0 problems

Post by odroid »

Do you know the USB-to-SATA bridge controller IC part number in the Orico enclosure?
We had a very similar issue with an Orico 2.5" HDD/SSD enclosure which had a bad controller IC of really poor compatibility with Linux.

obinary
Posts: 8
Joined: Tue Aug 04, 2020 7:58 am
languages_spoken: english
ODROIDs: ODROID-H2+
Has thanked: 0
Been thanked: 2 times
Contact:

Re: USB 3.0 problems

Post by obinary »

Hi Odroid,

With

Code: Select all

lsusb
I get this part number: ID 152d:0561

domih
Posts: 426
Joined: Mon Feb 11, 2019 4:48 pm
languages_spoken: English, French
ODROIDs: UX4, HC2, N2, N2+, H2, H2+, C4, HC4 - 1GbE, 2.5GbE, 10GbE, 40+GbE
Location: San Francisco Bay Area
Has thanked: 164 times
Been thanked: 159 times
Contact:

Re: USB 3.0 problems

Post by domih »

obinary wrote:
Sun Sep 12, 2021 7:45 am
Hi Odroid,

With

Code: Select all

lsusb
I get this part number: ID 152d:0561
If lsusb returns 152d:0561 it means you're using https://devicehunt.com/view/type/usb/ve ... evice/0561 which is a JMS551 - Sharkoon SATA QuickPort Duo.

But you stated: "...Orico uses JMicron JMS561U..." as shown in the amazon.es page you mentioned.

An English version of the description can be found there: https://pcper.com/2020/02/orico-usb-har ... on-review/ or there: https://www.orico.cc/us/product/detail/3553.html or https://www.orico.me/product/orico-3-5- ... -6239u3-c/.

Where did you find out it's using a JMS561U?

152d:0561 refers to the JMS551 - Sharkoon SATA QuickPort Duo
152d:1561 refers to the JMS561U two ports SATA 6Gb/s bridge

So lsusb should return two lines with 152D:1561, not 152D:0561.

(1) Could you post 2 photos of the USB bay: one overall and one where the model number appears?

(2) Looking at the board, can you find the JMicron chip and read/take a photo of what's on it?


---

(3) Could (re)-post the complete result of:
...# lsusb
then:
...# lsusb -t

---

IMHO, doing RAID 0 over USB -> SATAIII with Linux is playing with fire. The USB -> SATAIII chipsets on Linux are not the best things in the world. Depending on the chipset the protocol(s) implementation is not that good and the kernel implementation suffers as a consequence.

(4) Do you already have other SATA disks connected to the onboard two SATA ports?

(5) I assume you do RAID0 with mdadm?

---

(6) I assume the bays are separately powered. Yes?

---

Pending the resolution of what's above, you might want to experiment with the Linux USB Quirks.

Dig into https://www.bing.com/search?q=linux+usb ... 52d%3A0561 if the vendor_id:device_id is indeed 152d:0561 (to be confirmed).

And possibly dig into search.php?keywords=152d%3A0561 if ditto.

HTH

Domi

obinary
Posts: 8
Joined: Tue Aug 04, 2020 7:58 am
languages_spoken: english
ODROIDs: ODROID-H2+
Has thanked: 0
Been thanked: 2 times
Contact:

Re: USB 3.0 problems

Post by obinary »

Hi Domih,

Good catch. According to devicehunt.com, lsusb shows a different part ID :warning:

(3) It's weird, I also checked with a Raspberry Pi 4 with same results. Here are the lsusb and lsusb -t outputs:
Bus 002 Device 002: ID 152d:0561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS551 - Sharkoon SATA QuickPort Duo
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
| Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
| Port 2: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

(1) Overall photos (model number):
Image
Image

(2) JMicron JMS561U chip photos:
Image
Image

(4) I only have plugged one Orico Dual Bay per USB 3.0 port.

(5) Yes, I'm using mdadm.

(6) Yes, they are powered separately.

domih
Posts: 426
Joined: Mon Feb 11, 2019 4:48 pm
languages_spoken: English, French
ODROIDs: UX4, HC2, N2, N2+, H2, H2+, C4, HC4 - 1GbE, 2.5GbE, 10GbE, 40+GbE
Location: San Francisco Bay Area
Has thanked: 164 times
Been thanked: 159 times
Contact:

Re: USB 3.0 problems

Post by domih »

It would not be the first time that ven_ID:dev_ID is NOT exactly what you should expect.

Now that it is established you use a 6239C3-C with JMS561U, would you try with both UAS and ASMP off? Then UAS on and ASMP off?

ASMP: viewtopic.php?p=320336#p320336 (and lower your expectation, it is just a shot in the dark)

Then dig into https://www.bing.com/search?q=linux+usb+quirks+JMS561U

HTH

Domi

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: No registered users and 1 guest