GL-MT1300 won't recognize USB ssd. GL-AR750S works with same drive

I’ve having an issue where my Sandisk Extreme Portable SSD isn’t “recognized” on the GL-MT1300 usb port. I’ve looked at fdisk command. but no disk is shown. If I insert a microsd card, it does display in fdisk.

However, when I put the same drive on my Slate’s usb port, it’s recognized, it mounts, I can share it over the network, etc. Everything works. The drive is formatted NTFS, works and is visible in windows.

Both the Beryl and the Slate have latest updated firmware. What would cause the newer device not the see the drive, especially since the Beryl has a usb 3.0 port?

Can you give the log of both router when connected the usb disk?

ssh to the router and use logread

Slate:
Wed Apr 21 23:44:59 2021 kern.info kernel: [ 1779.426179] usb 1-1: new high-speed USB device number 2 using ehci-platform
Wed Apr 21 23:45:00 2021 daemon.err stubby[2024]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Wed Apr 21 23:45:00 2021 daemon.err stubby[2024]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Wed Apr 21 23:45:00 2021 kern.info kernel: [ 1779.641809] scsi host1: uas

Wed Apr 21 23:45:01 2021 kern.notice kernel: [ 1780.724896] scsi 1:0:0:0: Direct-Access SanDisk Extreme 55AE 3000 PQ: 0 ANSI: 6
Wed Apr 21 23:45:01 2021 kern.notice kernel: [ 1780.750820] scsi 1:0:0:1: Enclosure SanDisk SES Device 3000 PQ: 0 ANSI: 6
Wed Apr 21 23:45:01 2021 kern.notice kernel: [ 1780.761092] sd 1:0:0:0: [sdb] 3906963617 512-byte logical blocks: (2.00 TB/1.82 TiB)
Wed Apr 21 23:45:01 2021 daemon.err stubby[2024]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Wed Apr 21 23:45:01 2021 daemon.err stubby[2024]: Could not schedule query: None of the configured upstreams could be used to send queries on the specified transports
Wed Apr 21 23:45:01 2021 kern.notice kernel: [ 1780.788701] sd 1:0:0:0: [sdb] Write Protect is off
Wed Apr 21 23:45:01 2021 kern.debug kernel: [ 1780.793854] sd 1:0:0:0: [sdb] Mode Sense: 37 00 10 00
Wed Apr 21 23:45:01 2021 kern.notice kernel: [ 1780.801458] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Wed Apr 21 23:45:01 2021 kern.info kernel: [ 1780.834105] sd 1:0:0:0: [sdb] Optimal transfer size 1048576 bytes
Wed Apr 21 23:45:01 2021 kern.info kernel: [ 1780.881692] sdb: sdb1
Wed Apr 21 23:45:01 2021 kern.notice kernel: [ 1780.896571] sd 1:0:0:0: [sdb] Attached SCSI disk

Beryl:
Nothing from after I connected the USB. I waited 5 minutes and checked again, still nothing.

Here is dmesg output:

[10192.290723] usb 2-1: new SuperSpeed USB device number 6 using xhci-mtk
[10192.326381] scsi host3: uas
[10192.331815] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for unknown stream ring slot 1 ep 6
[10192.340245] xhci-mtk 1e1c0000.xhci: @000000000ecfe640 0c2a6000 00000000 05000000 01078000
[10192.348388] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for unknown stream ring slot 1 ep 2
[10192.356792] xhci-mtk 1e1c0000.xhci: @000000000ecfe650 0c2a6100 00000000 05000000 01038000
[10213.779505] scsi 3:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[10213.787084] scsi 3:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
[10213.793372] xhci-mtk 1e1c0000.xhci: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
[10213.803161] xhci-mtk 1e1c0000.xhci: ep deq seg = 8b704900, deq ptr = ab88e010
[10213.859462] scsi host3: uas_eh_device_reset_handler start
[10213.864891] xhci-mtk 1e1c0000.xhci: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
[10213.874676] xhci-mtk 1e1c0000.xhci: ep deq seg = 8b704f80, deq ptr = ab476010
[10214.030101] usb 2-1: reset SuperSpeed USB device number 6 using xhci-mtk
[10214.061360] scsi host3: uas_eh_device_reset_handler success
[10214.066979] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for unknown stream ring slot 1 ep 6
[10214.075383] xhci-mtk 1e1c0000.xhci: @000000000ecfe7b0 0c2a6200 00000000 05000000 01078000
[10214.089450] scsi 3:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[10214.096737] scsi 3:0:0:0: tag#0 CDB: opcode=0x0 00 00 00 00 00 00
[10214.102829] scsi host3: uas_eh_device_reset_handler start
[10214.108266] xhci-mtk 1e1c0000.xhci: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
[10214.118052] xhci-mtk 1e1c0000.xhci: ep deq seg = 8c5ab780, deq ptr = ab476010
[10214.269568] usb 2-1: reset SuperSpeed USB device number 6 using xhci-mtk
[10214.301332] scsi host3: uas_eh_device_reset_handler success
[10214.306917] scsi 3:0:0:0: Device offlined - not ready after error recovery

I’ve had the same problem with a usb ssd, I’ve found a workaround but no solution. This thread FS#1305 - Not working UAS driver for usb hdd case ORICO 2599US3-V1 · Issue #6243 · openwrt/openwrt · GitHub explains a bit about it and give two solutions. Only the second one works in my case and doesn’t survive a reboot. What worked is this command echo 357d:7788:u > /sys/module/usb_storage/parameters/quirks but replace 357d:7788 with your own VID:PID after you do this plug the device into the router.

1 Like

Put it in rc.local and it should survive a reboot.

@funfun where is rc.local located?

/etc/rc.local 
1 Like

What needs to go in the rc.local file and where does it need to be placed for when rebooting it mounts the drive?

First you need to determine your vendor id and product id for a Samsung t5 ssd. This process will be different depending on your environment so use Google to find out how.

I just wish there was a step by step tutorial because I feel like I’m not the only one is that having this problem or there needs to be a page for supported ssd/hard drives.

did you try installing “usb-utils” and do an lsusb?
on a far off note, maybe there might be something in usb-utils to straighten out the error.

or pci-utils…I call it idea cannon resolutions…shoot a bunch of crap and see if ya hit something. good luck