Usb 3 passthrough not working pve5.1

Cecil

Well-Known Member
Sep 22, 2017
57
2
48
45
I'm trying to move a large amount of data on to a new windows 2016 server via usb 3 but I cannot get the host port to pass through.
The last line: usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd just keeps repeating over and over and the drive letter shows up in windows but stops responding when trying to access it.

here is a dmesg log:

[79500.343935] usb 2-6: new SuperSpeed USB device number 2 using xhci_hcd
[79500.364654] usb 2-6: New USB device found, idVendor=0bc2, idProduct=3312
[79500.364659] usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[79500.364662] usb 2-6: Product: Expansion Desk
[79500.364664] usb 2-6: Manufacturer: Seagate
[79500.364667] usb 2-6: SerialNumber: NA4KYMV6
[79500.388774] usbcore: registered new interface driver usb-storage
[79500.396362] scsi host18: uas
[79500.396512] usbcore: registered new interface driver uas
[79500.397550] scsi 18:0:0:0: Direct-Access Seagate Expansion Desk 0739 PQ: 0 ANSI: 6
[79500.440312] sd 18:0:0:0: Attached scsi generic sg3 type 0
[79500.491108] sd 18:0:0:0: [sdc] Spinning up disk...
[79505.979778] .
[79507.034880] .
[79508.090372] .
[79509.145837] .
[79510.201028] .
[79511.256724] .
[79512.311388] .
[79513.366745] .
[79514.416212] .
[79515.498109] .
[79516.577045] .
[79516.594019] ready
[79516.594754] sd 18:0:0:0: [sdc] 1220942645 4096-byte logical blocks: (5.00 TB/4.55 TiB)
[79516.595170] sd 18:0:0:0: [sdc] Write Protect is off
[79516.595174] sd 18:0:0:0: [sdc] Mode Sense: 2b 00 10 08
[79516.596013] sd 18:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
[79516.639822] sdc: sdc1
[79516.659154] sd 18:0:0:0: [sdc] Attached SCSI disk
[80747.877797] vmbr0: port 2(tap1010i0) entered disabled state
[80791.829330] device tap1010i0 entered promiscuous mode
[80791.854112] vmbr0: port 2(tap1010i0) entered blocking state
[80791.854117] vmbr0: port 2(tap1010i0) entered disabled state
[80791.854647] vmbr0: port 2(tap1010i0) entered blocking state
[80791.854650] vmbr0: port 2(tap1010i0) entered forwarding state
[80792.728093] sd 18:0:0:0: [sdc] Synchronizing SCSI cache
[80792.966498] sd 18:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[80796.227669] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[80796.437730] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[80830.035780] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd
[80830.175632] usb 2-6: reset SuperSpeed USB device number 2 using xhci_hcd


I also tried adding the drive to the running VM with:

# device_add nec-usb-xhci,id=xhci,addr=0x1B,bus=pci.1
# device_add usb-host,bus=xhci.0,vendorid=0x0bc2,productid=0x3312,id=test

based on usb-devices command:
T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=01 Dev#= 3 Spd=5000 MxCh= 0
D: Ver= 3.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs= 1
P: Vendor=0bc2 ProdID=3312 Rev=07.39
S: Manufacturer=Seagate
S: Product=Expansion Desk
S: SerialNumber=NA4KYMV6
C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=8mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usbfs

Attached is a screenshot of the devices showing up but as soon as I add it to the VM I get the same info in dmesg again:
usb 2-6: reset SuperSpeed USB device number 3 using xhci_hcd
 

Attachments

  • usb problem.JPG
    usb problem.JPG
    72.8 KB · Views: 16
Quick update that might help.

I have a win7 VM install as a test also so i mapped the same port to it (removed it from the win 2016 VM)
downloaded a generic usb3 driver from lenovo (its a lenovo server) for windows 7 and it worked!

The drive shows up, I can see the files etc and my dmesg log isn't spammed with resets. ?!

The only obvious difference between the VM setups I can think of is that I had to use EFI bios on server 2016 to get GPT disks for the 10 Tb partition.
The windows 7 VM is on default (seabios) .
 
I notice with the 5.1 update the forum is really busy dealing with issues but does anyone have some ideas of things I can try please?
Or maybe aiddtional commands etc to give more information.
 
try to update the usb drivers in the vm in the device manager, apart from that it is hard to say, never had this problem
 
My problem at the moment is I can't even get the windows VM to boot up when I enable the passthrough, it gets stuck trying to figure out the hardware and just never starts up.

There is no updated driver for windows 10 /server 2016 since usb3 is supposed to be native to those OS's.
The link provided is for win7/server2008 and that one works just fine already.
My problem is the server 2016 install.
 
Hi. I have the same problem with a Usb3 Hard disk. Trying with an Usb2 hard disk working fine. Any idea? Thanks.
 
I have not been playing with it much and basically just gave up.
IT worked perfectly fine in server 2008 and windows 7 but server 2016's built in usb 3 driver does not play well with proxmox. I need to test this again but just haven't had time.