Describe the bug
I have an NVMe SSD USB-C Enclosure, specifically an LC-DOCK-C-M2 that I want to attach to my docker container to use as more "native storage".
However linux cannot intialize the device
7616.978844] usb 2-1: new SuperSpeed USB device number 9 using xhci-hcd
[ 7616.993206] usb 2-1: New USB device found, idVendor=152d, idProduct=0581, bcdDevice= 1.06
[ 7616.993243] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7616.993261] usb 2-1: Product: USB to ATA/ATAPI Bridge
[ 7616.993292] usb 2-1: Manufacturer: JMicron
[ 7616.993307] usb 2-1: SerialNumber: 0123456789ABCDEF
[ 7616.999902] scsi host0: uas
[ 7637.927212] scsi 0:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[ 7637.927405] scsi 0:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
[ 7637.928581] xhci-hcd 4000c000.usb: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
[ 7637.928672] xhci-hcd 4000c000.usb: ep deq seg = 00000000e1aa7a5f, deq ptr = 0000000070dfe7b1
[ 7637.932396] scsi host0: uas_eh_device_reset_handler start
[ 7637.932880] xhci-hcd 4000c000.usb: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
[ 7637.932967] xhci-hcd 4000c000.usb: ep deq seg = 0000000064ca7bc3, deq ptr = 00000000a329bce4
[ 7638.045901] usb 2-1: reset SuperSpeed USB device number 9 using xhci-hcd
[ 7638.065403] scsi host0: uas_eh_device_reset_handler success
[ 7638.066214] scsi 0:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[ 7638.066257] scsi 0:0:0:0: tag#0 CDB: opcode=0x0 00 00 00 00 00 00
[ 7638.066274] scsi host0: uas_eh_device_reset_handler start
[ 7638.066565] usb 2-1: cmd cmplt err -2
[ 7638.066801] xhci-hcd 4000c000.usb: Mismatch between completed Set TR Deq Ptr command & xHCI internal state.
[ 7638.066834] xhci-hcd 4000c000.usb: ep deq seg = 00000000d062c320, deq ptr = 00000000568ef1ee
[ 7638.183566] usb 2-1: reset SuperSpeed USB device number 9 using xhci-hcd
[ 7638.200526] scsi host0: uas_eh_device_reset_handler success
[ 7638.200574] scsi 0:0:0:0: Device offlined - not ready after error recovery
I tried quirks to disable link power management and thin provisioning but this didn't help
The disk is recognized in macOS just fine.
I verified the external power supply is connected and working.
To Reproduce
Attach an NVMe with the enclosure to docker
check dmesg for initialization errors
Expected behavior
the uas driver should initialize the disk
Diagnostic report (REQUIRED)
OrbStack info:
Version: 2.2.1
Commit: 0e182b501fcd9e05b99ffb363fce03610390c400 (v2.2.1)
System info:
macOS: 26.5.2 (25F84)
CPU: arm64, 12 cores
CPU model: Apple M4 Pro
Model: Mac16,8
Memory: 24 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2026-07-16T08-17-45.868849Z.zip
Screenshots and additional context (optional)
No response
Describe the bug
I have an NVMe SSD USB-C Enclosure, specifically an LC-DOCK-C-M2 that I want to attach to my docker container to use as more "native storage".
However linux cannot intialize the device
I tried quirks to disable link power management and thin provisioning but this didn't help
The disk is recognized in macOS just fine.
I verified the external power supply is connected and working.
To Reproduce
Attach an NVMe with the enclosure to docker
check dmesg for initialization errors
Expected behavior
the uas driver should initialize the disk
Diagnostic report (REQUIRED)
OrbStack info:
Version: 2.2.1
Commit: 0e182b501fcd9e05b99ffb363fce03610390c400 (v2.2.1)
System info:
macOS: 26.5.2 (25F84)
CPU: arm64, 12 cores
CPU model: Apple M4 Pro
Model: Mac16,8
Memory: 24 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2026-07-16T08-17-45.868849Z.zip
Screenshots and additional context (optional)
No response