External SSD over USB 3 not getting recognized

[ericswpark]

I'm running into a weird issue with the latest updated Proxmox install where a USB 3 SSD (Samsung T5) passed through to a VM will not be recognized on the VM itself. The guest OS is Arch Linux, and this is what I get on the dmesg:

[    3.125565] usbcore: registered new interface driver usb-storage
[    3.150918] usb 3-1: Not enough host controller resources for new device state.
[    3.151180] xhci_hcd 0000:02:1b.0: xHCI xhci_drop_endpoint called with disabled ep (____ptrval____)
[    3.151188] xhci_hcd 0000:02:1b.0: xHCI xhci_drop_endpoint called with disabled ep (____ptrval____)
[    3.151194] xhci_hcd 0000:02:1b.0: xHCI xhci_drop_endpoint called with disabled ep (____ptrval____)
[    3.151238] xhci_hcd 0000:02:1b.0: Trying to add endpoint 0x81 without dropping it.
[    3.151249] usb 3-1: Not enough bandwidth for altsetting 0
[    3.168945] uas 3-1:1.0: probe with driver uas failed with error -12
[    3.169014] usbcore: registered new interface driver uas

For some weird reason, editing the machine type and downgrading it to i440fx-5.1 or so allows me to enable the USB 3 checkbox when passing the drive through, which "fixes" it, although I think I remember seeing a dmesg entry about the drive running in reduced performance mode.

Was wondering if anybody else was running into this issue?

 

[Andeos]

I'm having this exact same issue, running on arm64. Have you found a fix?

 

[ericswpark]

I'm having this exact same issue, running on arm64. Have you found a fix?

Unfortunately not. My machine is a HP T620 thin client of all things, x86_64 arch.

For a temporary workaround I've formatted the drive as a LVM-thin and moved over my VM onto it, then expanded the size. Would be great if I could mount it within a VM, though.

 

[ericswpark]

I had some time today to try with a new VM running NixOS, to pass through the drive properly and not have to store the actual VM image on the drive itself.

Unfortunately, I'm still getting the following error on the latest Linux kernel obtainable on NixOS (6.13.4) and with the machine type set to the default pc-i440fx-latest:

[   14.295489] usb 3-1: Not enough host controller resources for new device state.
[   14.296382] xhci_hcd 0000:02:1b.0: xHCI xhci_drop_endpoint called with disabled ep 00000000174c4ad1
[   14.296392] xhci_hcd 0000:02:1b.0: xHCI xhci_drop_endpoint called with disabled ep 00000000bce7cdac
[   14.296399] xhci_hcd 0000:02:1b.0: xHCI xhci_drop_endpoint called with disabled ep 000000004251e967
[   14.296440] xhci_hcd 0000:02:1b.0: Trying to add endpoint 0x81 without dropping it.
[   14.296450] usb 3-1: Not enough bandwidth for altsetting 0
[   14.322031] uas 3-1:1.0: probe with driver uas failed with error -12
[   14.325602] usbcore: registered new interface driver uas

I then tried all the different versions in descending order. At pc-i440fx-7.0, I finally get the following message printed to `dmesg`:

[   14.029597] usb 3-1: USB controller 0000:02:1b.0 does not support streams, which are required by the UAS driver.
[   14.029611] usb 3-1: Please try an other USB controller if you wish to use UAS.
[   14.029615] usb-storage 3-1:1.0: USB Mass Storage device detected
[   14.062047] scsi host3: usb-storage 3-1:1.0
[   14.062415] usbcore: registered new interface driver usb-storage
[   14.355955] usbcore: registered new interface driver uas
[   14.576053] bochs-drm 0000:00:02.0: [drm] fb0: bochs-drmdrmfb frame buffer device
[   15.081087] scsi 3:0:0:0: Direct-Access     Samsung  Portable SSD T5  0    PQ: 0 ANSI: 6
[   15.087812] sd 3:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[   15.090024] sd 3:0:0:0: [sdb] Write Protect is off
[   15.090034] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00
[   15.093035] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   15.106273] sd 3:0:0:0: [sdb] Attached SCSI disk

There was a thread on Reddit 4 months ago (https://www.reddit.com/r/Proxmox/comments/1g5lwi9/usb_301_passthrough_with_error/) with the exact same issue, and unfortunately the poster gave up on fixing the bug. If the Proxmox team could look into this and give any guidance on how to track down what is going wrong that would be greatly appreciated!

EDIT: forgot to mention: Proxmox on the host has been updated to the latest version available for the community version (8.3.4) and all packages were updated, but this made no difference.