Same errors here with Win10 host, VBox 5.2.6 (and corresponding GA + Extension Pack), Debian 9 guest.
I have followed the instructions at the afore-linked "USB basics and troubleshooting page", and nothing there fixes the problem or sheds quite enough light on this problem. The only thing I know of that I haven't yet done is to verify that a native debian 9 install can mount this USB 3 drive.
To review, here is what I'm doing:
1. Insert USB 3 flash drive (into USB 3 "SS" port), prove it works fine in Windows, "Eject" drive in Windows Explorer
2. Open VBox VM settings, USB tab:
a. "Enable USB Controller" is checked, with USB 2 (EHCI) selected
b. Add filter, choose my device from list (PNY USB 3.0 FD [0100]), edit filter to Delete all values except Name, VendorID and ProductID.
c. Save settings
3. Unplug USB 3 flash drive
4. Start guest VM, login, tail -f /var/log/syslog
5. Plug in USB 3 flash drive
6. Filter is "working" in that the host does NOT mount the drive, however the Debian 9 guest also does NOT mount the drive, syslog shows:
Code: Select all
Feb 5 13:19:55 tblack-stretch kernel: [ 631.825255] usb 1-1: new high-speed USB device number 6 using ehci-pci
Feb 5 13:19:55 tblack-stretch kernel: [ 632.073892] usb 1-1: device descriptor read/64, error 18
Feb 5 13:19:56 tblack-stretch kernel: [ 632.445037] usb 1-1: device descriptor read/64, error 18
Feb 5 13:19:56 tblack-stretch kernel: [ 632.793226] usb 1-1: new high-speed USB device number 7 using ehci-pci
Feb 5 13:19:56 tblack-stretch kernel: [ 633.045335] usb 1-1: device descriptor read/64, error 18
Feb 5 13:19:57 tblack-stretch kernel: [ 633.473260] usb 1-1: device descriptor read/64, error 18
Feb 5 13:19:57 tblack-stretch kernel: [ 633.822564] usb 1-1: new high-speed USB device number 8 using ehci-pci
Feb 5 13:19:57 tblack-stretch kernel: [ 633.860040] usb 1-1: Invalid ep0 maxpacket: 9
Feb 5 13:19:58 tblack-stretch kernel: [ 634.105774] usb 1-1: new high-speed USB device number 9 using ehci-pci
Feb 5 13:19:58 tblack-stretch kernel: [ 634.149770] usb 1-1: Invalid ep0 maxpacket: 9
Feb 5 13:19:58 tblack-stretch kernel: [ 634.162388] usb usb1-port1: unable to enumerate USB device
7. lsusb shows a "Linux Foundation 2.0 root hub"
8. shutdown guest. I then notice that the host mounts the drive (still plugged in) (I believe this behavior is expected)
I have repeated above steps except substituting 2a as:
a. "Enable USB Controller" is checked, with USB 3 xHCI selected
and the result is identical (except that the syslog read error entries show "usb 1-2" instead of "usb 1-1" (as expected I believe), and lsusb shows a "Linux Foundation 3.0 root hub" (also as expected) )
More details:
* I've ensured my user is in vboxusers group.
* I will attach my vbox logs after this post.
* Output of "VBoxManager list usbhost" with USB flash drive connected includes the device:
Code: Select all
PS C:\Program Files\Oracle\VirtualBox> .\VBoxManage.exe list usbhost
Host USB Devices:
UUID: debd29c1-607f-498a-86fb-23802d4a3d26
VendorId: 0x1bcf (1BCF)
ProductId: 0x000a (000A)
Revision: 6.18 (0618)
Port: 6
USB version/speed: 2/High
Manufacturer: Sunplus Innovation Technology Inc.
Product: USB Laser Wheel Mouse
Address: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0000
Current State: Busy
UUID: a1e971ee-7c13-4552-87f9-31ebbd1c9e2e
VendorId: 0x154b (154B)
ProductId: 0x00d2 (00D2)
Revision: 1.0 (0100)
Port: 22
USB version/speed: 3/Super
Manufacturer: PNY
Product: USB 3.0 FD
SerialNumber: 07037BB8BB3A8956
Address: {36fc9e60-c465-11cf-8056-444553540000}\0008
Current State: Busy
UUID: 06596964-66d9-4c65-8531-a11046821f72
VendorId: 0x0a12 (0A12)
ProductId: 0x0001 (0001)
Revision: 136.145 (136145)
Port: 7
USB version/speed: 2/High
Manufacturer: Cambridge Silicon Radio, Ltd
Product: Bluetooth Dongle (HCI mode)
Address: {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}\0000
Current State: Busy
UUID: 2d670806-3471-46b2-be12-96946c35f44d
VendorId: 0x0483 (0483)
ProductId: 0x5710 (5710)
Revision: 2.0 (0200)
Port: 4
USB version/speed: 2/High
Manufacturer: STMicroelectronics
Product: obins anne keyboard
SerialNumber: STM32
Address: {36fc9e60-c465-11cf-8056-444553540000}\0002
Current State: Busy
UUID: f8971d71-28e1-4516-bba7-0d5b62f6e0a1
VendorId: 0x0403 (0403)
ProductId: 0x6001 (6001)
Revision: 6.0 (0600)
Port: 5
USB version/speed: 2/High
Manufacturer: FTDI
Product: TTL232R-3V3
SerialNumber: FTH0C51L
Address: {36fc9e60-c465-11cf-8056-444553540000}\0007
Current State: Busy
Please help.
EDIT:
* I confirmed this drive mounts fine in Ubuntu 16, connected to a usb 2 port.
* Then I found
this post on Debian 9 USB 3 errors, and then thought to try same steps but in step 1. plug into a 2.0 port instead of 3.0 port.... et voila! she mounts!
Code: Select all
Feb 5 14:02:48 tblack-stretch kernel: [ 48.646375] usb 1-2: new high-speed USB device number 3 using xhci_hcd
Feb 5 14:02:48 tblack-stretch kernel: [ 49.001890] usb 1-2: New USB device found, idVendor=154b, idProduct=00d2
Feb 5 14:02:48 tblack-stretch kernel: [ 49.001894] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 5 14:02:48 tblack-stretch kernel: [ 49.001896] usb 1-2: Product: USB 3.0 FD
Feb 5 14:02:48 tblack-stretch kernel: [ 49.001898] usb 1-2: Manufacturer: PNY
Feb 5 14:02:48 tblack-stretch kernel: [ 49.001899] usb 1-2: SerialNumber: 07037BB8BB3A8956
Feb 5 14:02:48 tblack-stretch mtp-probe: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:0c.0/usb1/1-2"
Feb 5 14:02:48 tblack-stretch mtp-probe: bus: 1, device: 3 was not an MTP device
Feb 5 14:02:48 tblack-stretch kernel: [ 49.022367] usb-storage 1-2:1.0: USB Mass Storage device detected
Feb 5 14:02:48 tblack-stretch kernel: [ 49.022777] scsi host4: usb-storage 1-2:1.0
Feb 5 14:02:48 tblack-stretch kernel: [ 49.022828] usbcore: registered new interface driver usb-storage
Feb 5 14:02:48 tblack-stretch kernel: [ 49.024102] usbcore: registered new interface driver uas
Feb 5 14:02:50 tblack-stretch kernel: [ 50.549598] scsi 4:0:0:0: Direct-Access PNY USB 3.0 FD PMAP PQ: 0 ANSI: 6
Feb 5 14:02:50 tblack-stretch kernel: [ 50.549960] sd 4:0:0:0: Attached scsi generic sg2 type 0
Feb 5 14:02:50 tblack-stretch kernel: [ 50.551085] sd 4:0:0:0: [sdb] 30343168 512-byte logical blocks: (15.5 GB/14.5 GiB)
Feb 5 14:02:50 tblack-stretch kernel: [ 50.554450] sd 4:0:0:0: [sdb] Write Protect is off
Feb 5 14:02:50 tblack-stretch kernel: [ 50.554451] sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00
Feb 5 14:02:50 tblack-stretch kernel: [ 50.557997] sd 4:0:0:0: [sdb] No Caching mode page found
Feb 5 14:02:50 tblack-stretch kernel: [ 50.558067] sd 4:0:0:0: [sdb] Assuming drive cache: write through
Feb 5 14:02:50 tblack-stretch kernel: [ 50.569286] sdb: sdb1
Feb 5 14:02:50 tblack-stretch kernel: [ 50.577757] sd 4:0:0:0: [sdb] Attached SCSI removable disk
..and the device now shows up in the output of lsusb, lsblk, and I can mount it.
So, the question remains... what is the problem with using a USB 3.0 port with Windows 10 host, Debian Guest?