USB 3 Drive not recognized on USB 3 port

[wand3r3r]

Not a Windows guy for sure but I believe you need to post another guest log with the software removed and it may not hurt to post the hardening log as well so the Windows gurus can see them..

Unfortunately I don't have access to a hardening log.
Here is an updated copy of the VBox from both machines

[wand3r3r]

Are you plugging the device into some kind of a hub? The problem is that you capture the device and it immediately vanishes, as if it were unplugged. It's relatively unlikely that it can be fixed on the VirtualBox side.

No. Directly into the ports on the machine.
I may have unplugged it rather quickly 10 to 30 seconds later. But not as quickly as is shown.

My sytem does have Symantec Endpoint Encryption. And every time I plug the device in and alert pops up saying that it is copying a "Removable Media Access Utility" file to the drive. But even with that it still works in the USB2.0 port.

[wand3r3r]

Are you plugging the device into some kind of a hub? The problem is that you capture the device and it immediately vanishes, as if it were unplugged. It's relatively unlikely that it can be fixed on the VirtualBox side.

That is strange.. I'm plugging directly into the usb on the laptop. I tried it again making sure not to detach it so quickly

00:06:35.016205 VUSB: Attached '0000000004e488a0[proxy 1f75:0917]' to port 2 --- USB 3.0 Port 1 -- Does not work
00:07:22.842322 VUSB: Detached '0000000004e488a0[proxy 1f75:0917]' from port 2
00:08:22.723359 VUSB: Attached '0000000004e488a0[proxy 1f75:0917]' to port 2 --- USB 3.0 Port 2 Does not work
00:08:56.864992 VUSB: Detached '0000000004e488a0[proxy 1f75:0917]' from port 2
00:09:38.495964 VUSB: Attached '0000000004e488a0[proxy 1f75:0917]' to port 2 --- USB 2.0 Port 1 DOES work
00:10:14.025041 VUSB: Detached '0000000004e488a0[proxy 1f75:0917]' from port 2
00:10:44.938903 VUSB: Attached '0000000004e488a0[proxy 1f75:0917]' to port 2 -- USB 2.0 Port 2 DOES work
00:11:10.759815 VUSB: Detached '0000000004e488a0[proxy 1f75:0917]' from port 2

[mpack]

The log says that the Ubuntu version is 14.04, not 16.04 as you said in your first post. Can you say which version is correct?

I would still like a clarification on this.

[wand3r3r]

That is just the folder name when the VM was created. It has been upgraded since then.

Code: Select all

$ lsb_release -d
Description:	Ubuntu 16.04.2 LTS

[michaln]

Did I miss it or was it explained in detail somewhere in this thread what exactly "does not work" means?

[wand3r3r]

Did I miss it or was it explained in detail somewhere in this thread what exactly "does not work" means?

The drive is not available within the guest OS. The drive does not automount within the guest OS.
lsub
fdisk -l
cannot list the dive.

It seems as if the drive is not being passed to the OS.

[michaln]

And what's in the guest's dmesg output? I bet there is something...

[wand3r3r]

And what's in the guest's dmesg output? I bet there is something...

There does seem to be something..

[ 371.220640] usb 1-2: new high-speed USB device number 7 using xhci_hcd
[ 371.396874] usb 1-2: device descriptor read/64, error 18
[ 371.672600] usb 1-2: device descriptor read/64, error 18
[ 371.948202] usb 1-2: new high-speed USB device number 8 using xhci_hcd
[ 372.128749] usb 1-2: device descriptor read/64, error 18
[ 372.414814] usb 1-2: device descriptor read/64, error 18
[ 372.690362] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[ 372.703685] usb 1-2: Invalid ep0 maxpacket: 9
[ 372.875923] usb 1-2: new high-speed USB device number 10 using xhci_hcd
[ 372.891858] usb 1-2: Invalid ep0 maxpacket: 9
[ 372.891941] usb usb1-port2: unable to enumerate USB device

[erdeslawe]

Doesn't that Error 18 mean that the PC's USB Port can't provide sufficient power to operate the connected USB device?

[wand3r3r]

Doesn't that Error 18 mean that the PC's USB Port can't provide sufficient power to operate the connected USB device?

The device descriptor read/64, error -110 means that USB port power supply was exceeded. http://askubuntu.com/questions/644010/u ... -error-110

It looks like error has been reported here before:
viewtopic.php?f=1&t=49060
Listed as fixed here:
https://www.virtualbox.org/ticket/12274
From ubuntuforums:
http://askubuntu.com/questions/783076/u ... virtualbox

[michaln]

It looks like error has been reported here before:
viewtopic.php?f=1&t=49060
Listed as fixed here:
https://www.virtualbox.org/ticket/12274

No. That problem was trying to use a USB 3.0 device in a guest with no USB 3.0 support. That is not the OP's problem because the OP does have USB 3.0 enabled in a VM.

Except... except... it is a similar problem because looking closer, there's this: "new high-speed USB device number 7 using xhci_hcd". What that means is that the guest OS thinks it's a high-speed aka USB 2.0 device, but in reality it's apparently a superspeed (USB 3.0) device. That's also why the device works when it's plugged into a non-USB3-capable port on the host because then there's no discrepancy. But the guest already has xHCI (i.e. USB 3.0) support enabled, so enabling it won't fix the problem.

So... what's the output of 'VBoxManage list usbhost' on the host?

[michaln]

The problem is probably caused by the fact that the host OS (Windows 7) never got proper USB 3.0 support. What exactly is the xHCI controller on the host? Which vendor and driver? VirtualBox is known to work with Intel's xHCI drivers for Windows 7 (probably most common), but it's also known not to work with some other vendors' drivers.

[wand3r3r]

So... what's the output of 'VBoxManage list usbhost' on the host?

Code: Select all

[b]UUID:               a72804a1-0f8c-4b6a-a03d-6a58a8de6824
VendorId:           0x1f75 (1F75)
ProductId:          0x0917 (0917)
Revision:           0.1 (0001)
Port:               0
USB version/speed:  3/Super
Manufacturer:       UFD 3.0
Product:            Silicon-Power32G
SerialNumber:       P1601731000000000000000361
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0076
Current State:      Captured[/b]

UUID:               01c104e9-d4da-480e-8a8e-02e7867e7d32
VendorId:           0x138a (138A)
ProductId:          0x003d (003D)
Revision:           1.4 (0104)
Port:               0
USB version/speed:  1/Full
Manufacturer:       Validity Sensors, Inc.
Product:            VFS491
SerialNumber:       00204c5a348c
Address:            {ff5262c8-9032-4b05-92cf-9f53044592a6}\0000
Current State:      Busy

UUID:               db29b3be-a6e7-4ac7-b9e8-2c26b769e0d6
VendorId:           0x0a5c (0A5C)
ProductId:          0x21e1 (21E1)
Revision:           1.18 (0118)
Port:               0
USB version/speed:  2/High
Manufacturer:       Broadcom Corp
Product:            BCM20702A0
SerialNumber:       083E8E991405
Current State:      Available

UUID:               e721458a-07fa-4bc9-aac1-80e598e48bec
VendorId:           0x04f3 (04F3)
ProductId:          0x0213 (0213)
Revision:           81.37 (8137)
Port:               0
USB version/speed:  1/Full
Manufacturer:       Elan Microelectronics Corp.
Product:            PS/2+USB Mouse
Address:            {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0019
Current State:      Busy

UUID:               cb20abf8-8225-414d-9ded-4fab41f09956
VendorId:           0x04f2 (04F2)
ProductId:          0xb230 (B230)
Revision:           81.113 (81113)
Port:               0
USB version/speed:  2/High
Manufacturer:       Chicony Electronics Co., Ltd.
Product:            HP HD Webcam [Fixed]
SerialNumber:       SN0001
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0007
Current State:      Busy

UUID:               796f0775-bdab-4340-8755-3952b6b4d5ff
VendorId:           0x0430 (0430)
ProductId:          0x00a2 (00A2)
Revision:           1.3 (0103)
Port:               0
USB version/speed:  2/High
Manufacturer:       Sun Microsystems, Inc.
Product:            Sun USB Keyboard
Address:            {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0018
Current State:      Busy

[wand3r3r]

The problem is probably caused by the fact that the host OS (Windows 7) never got proper USB 3.0 support. What exactly is the xHCI controller on the host? Which vendor and driver? VirtualBox is known to work with Intel's xHCI drivers for Windows 7 (probably most common), but it's also known not to work with some other vendors' drivers.

Both PCs I tired it on are Windows 7 PCs. One is an HP8770 and the other is a Dell 7710. The attached image is from the HP

The driver for the root hub and the host controller on the HPC seem to be:
1.0.6.245
10/15/2012 8:00:00 PM

The dell has the same USB3 root hub and host controller but the driver version is
4.0.0.36
6/15/2015