USB Devicea - Failed to Attach device

Discussions related to using VirtualBox on Linux hosts.

USB Devicea - Failed to Attach device

Postby WeManageIT » 30. Nov 2017, 16:49

I am having an issue with USB sticks or USB actual drives.

Linux Host 16.0.4.3 fully updated Kernel 4.10 4.10.0-40-generic #44~16.04.1-Ubuntu SMP Thu Nov 9 15:37:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

guest: winslobber 7 - fresh install
Guest Additions added
Installed from the VBOX REPO!

VBOX 5.2.2
When I attach a Seagate like 500GB or so drive or a 64GB USB Stick, I get
"Failed to attach <device> to virtual machine..."

If I SWITCH the USB setup from USB 2.0 to USB 3.0
The error disappears, BUT the devices do NOT ATTACH, and winpuke doesn't
attempt to add drivers to use these devices

On a 5.x setup on a different machine, the SAME DEVICES work fine, attach,
winpuke gets a driver, works.

user is in vboxusers group, or I wouldn't see the USB devices to start
This is causing major pains in transferring data into the box.

Actual PC is brand new Dell Inspiron-3655.
USB needs to work for devices, be it sticks, drives, cameras, or what not.
If this was my personal or work machine it wouldn't need that other
infestation, but its a last resort setup for when they get stuck in Linux.

Tried on a Linux Guest (*buntu 16.04) Same thing. USB 2.0 error message, "Can't attach..." V3.0 can't access device in the guest, notifier never shows up, device not seen.

Guest logs attached.
Attachments
vboxusberrors.zip
Linux and winslopper 7 logs
(153.82 KiB) Downloaded 2 times
Do NOT reply with the "POST REPLY" button, please use "QUOTE", on the post.
WeManageIT
 
Posts: 7
Joined: 28. Mar 2014, 19:51
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Linux Baby! LINUX!

Re: USB Devicea - Failed to Attach device

Postby Perryg » 30. Nov 2017, 18:01

Code: Select all   Expand viewCollapse view
00:01:04.626802 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to create a proxy device for the USB device. (Error: VERR_PDM_NO_USB_PORTS)}, preserve=false aResultDetail=0


Switch to USB3 after you install the USB3 drivers in Windows 7 ( not installed by default )

See previous post viewtopic.php?f=2&t=68847
Perryg
Site Moderator
 
Posts: 34266
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: USB Devicea - Failed to Attach device

Postby WeManageIT » 30. Nov 2017, 22:48

Perryg wrote:Switch to USB3 after you install the USB3 drivers in Windows 7 ( not installed by default )

See previous post viewtopic.php?f=2&t=68847


I've read that post, and I don't see a clear download this install this link. Lots of circuitious talk, and not enough clear dl this.

So is THIS what is to be downloaded:
http://www.dell.com/support/search/us/e ... langFacet=[en]
Or something else. I don't play with winturd stuff.

And the Linux guest? Which does the same things on Kernel 4.10, Linux has had USB 3.0 support since kernel 2.9.x and Karmic Koala.


Linux guest will NOT work with USB 2 or 3, devices connected to the host OS work fine. Via VBOX, don't. I think there is more to it than just a drivers issue in winslopper. Especially if the Linux guest would have worked. Linux guests do not work either.
Do NOT reply with the "POST REPLY" button, please use "QUOTE", on the post.
WeManageIT
 
Posts: 7
Joined: 28. Mar 2014, 19:51
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Linux Baby! LINUX!

Re: USB Devicea - Failed to Attach device

Postby socratis » 30. Nov 2017, 23:51

Please read the following thread: USB basics and troubleshooting, all of the posts. If you still have a problem after reading through the whole thing, please follow the advice of the last post.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 12648
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: USB Devicea - Failed to Attach device

Postby WeManageIT » 1. Dec 2017, 13:09

Trying to finish this install up, and some tesing.

On the Linux GUEST 16.04

here is what happens

Using the a FRONT PORT on the 3655,

Code: Select all   Expand viewCollapse view
cat usbNOTworking.log
[  150.284646] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[  150.314436] usb 2-1: New USB device found, idVendor=0bc2, idProduct=2340
[  150.314442] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  150.314446] usb 2-1: Product: Expansion+
[  150.314449] usb 2-1: Manufacturer: Seagate
[  150.314452] usb 2-1: SerialNumber: N
[  150.418832] usb 2-1: USB controller 0000:00:0c.0 does not support streams, which are required by the UAS driver.
[  150.418837] usb 2-1: Please try an other USB controller if you wish to use UAS.
[  150.418840] usb-storage 2-1:1.0: USB Mass Storage device detected
[  150.419105] scsi host3: usb-storage 2-1:1.0
[  150.421756] usbcore: registered new interface driver usb-storage
[  150.431705] usbcore: registered new interface driver uas
[  173.156719] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd


Does NOT WORK!

I had just left it in from transferring some other stuff to the REAL OS Linux Host.

Since I had a spare USB port on the REAR, tried it:

Code: Select all   Expand viewCollapse view
WORKS REAR PORTS
  707.173245] usb 1-2: new high-speed USB device number 3 using xhci_hcd
[  707.323400] usb 1-2: New USB device found, idVendor=0bc2, idProduct=2340
[  707.323406] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  707.323409] usb 1-2: Product: Expansion+
[  707.323413] usb 1-2: Manufacturer: Seagate
[  707.323415] usb 1-2: SerialNumber: N
[  707.329231] scsi host3: uas
[  707.331972] scsi 3:0:0:0: Direct-Access     Seagate  Expansion+       A200 PQ: 0 ANSI: 6
[  707.373389] sd 3:0:0:0: Attached scsi generic sg2 type 0
[  707.379852] sd 3:0:0:0: [sdb] 976773167 512-byte logical blocks: (500 GB/466 GiB)
[  707.379872] sd 3:0:0:0: [sdb] 4096-byte physical blocks
[  707.381786] sd 3:0:0:0: [sdb] Write Protect is off
[  707.381790] sd 3:0:0:0: [sdb] Mode Sense: 4f 00 00 00
[  707.383352] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  707.738369]  sdb: sdb1
[  707.746954] sd 3:0:0:0: [sdb] Attached SCSI disk


That to me makes no sense. The USB drive works fine in either port on the host. As basically the TWO PORTS that a non tech user is going to shove a USB stick or drive into, are basically useless. :evil:
Do NOT reply with the "POST REPLY" button, please use "QUOTE", on the post.
WeManageIT
 
Posts: 7
Joined: 28. Mar 2014, 19:51
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Linux Baby! LINUX!

Re: USB Devicea - Failed to Attach device

Postby WeManageIT » 1. Dec 2017, 14:08

socratis wrote:Please read the following thread: USB basics and troubleshooting, all of the posts. If you still have a problem after reading through the whole thing, please follow the advice of the last post.


I've read that, not helpful, but from the last post

Code: Select all   Expand viewCollapse view
$ id
uid=1000(nola) gid=1000(nola) groups=1000(nola),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),127(sambashare),128(vboxusers)
nola@nola-Inspiron-3655:~$ VBoxManage -version
5.2.2r119230
nola@nola-Inspiron-3655:~$ VBoxManage list extpacks
Extension Packs: 1
Pack no. 0:   Oracle VM VirtualBox Extension Pack
Version:      5.2.2
Revision:     119230
Edition:     
Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
VRDE Module:  VBoxVRDP
Usable:       true
Why unusable:
nola@nola-Inspiron-3655:~$ VBoxManage list usbhost
Host USB Devices:

UUID:               3bb81f75-b627-466c-ae88-c3f111775f81
VendorId:           0x413c (413C)
ProductId:          0x301a (301A)
Revision:           1.0 (0100)
Port:               2
USB version/speed:  2/Low
Manufacturer:       PixArt
Product:            Dell MS116 USB Optical Mouse
Address:            sysfs:/sys/devices/pci0000:00/0000:00:12.0/usb1/1-1/1-1.3//device:/dev/vboxusb/001/003
Current State:      Busy

UUID:               4d7222ea-6e13-49bd-833b-aca63ae80923
VendorId:           0x413c (413C)
ProductId:          0x2113 (2113)
Revision:           1.8 (0108)
Port:               3
USB version/speed:  1/Low
Manufacturer:       Dell Computer Corp.
Product:            Dell KB216 Wired Keyboard
Address:            sysfs:/sys/devices/pci0000:00/0000:00:12.0/usb1/1-1/1-1.4//device:/dev/vboxusb/001/004
Current State:      Busy

UUID:               bf62d5ce-4f15-4b38-81fd-7a328301ebca
VendorId:           0x0cf3 (0CF3)
ProductId:          0xe005 (E005)
Revision:           0.2 (0002)
Port:               0
USB version/speed:  1/Full
Manufacturer:       Qualcomm Atheros Communications
Address:            sysfs:/sys/devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1.1//device:/dev/vboxusb/002/005
Current State:      Busy

UUID:               a521ad8f-3d0a-4ebb-9192-0ec1f402e244
VendorId:           0x0bda (0BDA)
ProductId:          0x0129 (0129)
Revision:           57.96 (5796)
Port:               1
USB version/speed:  2/High
Manufacturer:       Generic
Product:            USB2.0-CRW
SerialNumber:       20
Address:            sysfs:/sys/devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1.2//device:/dev/vboxusb/002/004
Current State:      Busy

UUID:               03d99e8c-1253-4e8a-858f-be486070919b
VendorId:           0x0bc2 (0BC2)
ProductId:          0x2340 (2340)
Revision:           1.0 (0100)
Port:               1
USB version/speed:  2/High
Manufacturer:       Seagate
Product:            Expansion+
SerialNumber:       Noneofyourbusines
Address:            sysfs:/sys/devices/pci0000:00/0000:00:12.0/usb1/1-1/1-1.2//device:/dev/vboxusb/001/005
Current State:      Available

nola@nola-Inspiron-3655:~$ VBoxManage list usbfilters
Global USB Device Filters:

<none>

 VBoxManage showvminfo "Nola Win 7 PC"
Name:            Nola Win 7 PC
Groups:          /
Guest OS:        Windows 7 (64-bit)
UUID:            9b632eff-e830-40b4-a5d7-cf153b4981cd
Config file:     /home/nola/VirtualBox VMs/Nola Win 7 PC/Nola Win 7 PC.vbox
Snapshot folder: /home/nola/VirtualBox VMs/Nola Win 7 PC/Snapshots
Log folder:      /home/nola/VirtualBox VMs/Nola Win 7 PC/Logs
Hardware UUID:   9b632eff-e830-40b4-a5d7-cf153b4981cd
Memory size:     2048MB
Page Fusion:     off
VRAM size:       128MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  2
PAE:             on
Long Mode:       on
Triple Fault Reset: off
APIC:            on
X2APIC:          off
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Network
Boot Device (4): Floppy
ACPI:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: HyperV
State:           powered off (since 2017-12-01T00:57:36.963000000)
Monitor count:   1
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
SATA (0, 0): /home/nola/VirtualBox VMs/Nola Win 7 PC/Nola Win 7 PC.vdi (UUID: 08f68bf4-bf80-4fed-9ab0-25411a66b790)
SATA (1, 0): /usr/share/virtualbox/VBoxGuestAdditions.iso (UUID: 093edebc-7d22-4620-afd3-0a361ca8407b)
NIC 1:           MAC: 080027E0861C, Attachment: Bridged Interface 'enp1s0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: PulseAudio, Controller: HDA, Codec: STAC9221)
Audio playback:  disabled
Audio capture: enabled
Clipboard Mode:  disabled
Drag and drop Mode: disabled
VRDE:            disabled
USB:             disabled
EHCI:            disabled
XHCI:            enabled

USB Device Filters:

Index:            0
Active:           yes
Name:             Seagate Expansion+ [0100]
VendorId:         0bc2
ProductId:        2340
Revision:         0100
Manufacturer:     Seagate
Product:          Expansion+
Remote:           0
Serial Number:    Noneofourbusiness

Bandwidth groups:  <none>

Shared folders:  <none>

Capturing:          not active
Capture screens:    0
Capture file:       /home/nola/VirtualBox VMs/Nola Win 7 PC/Nola Win 7 PC.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25
Capture options:    ac_enabled=false

Guest:

Configured memory balloon size:      0 MB



You can read the follow up, on the Linux Guest as I used it as a test since Linux has all its drivers for USB3.0 ready to go. Still an issue.

Unresolved is winpuker driver for winslobber 7

What windpuker driver is needed and compatible with VB 5.2.2's emulated environment. The other thread just speciously talks about Some mythical Intel Driver, some dell driver.
Do NOT reply with the "POST REPLY" button, please use "QUOTE", on the post.
WeManageIT
 
Posts: 7
Joined: 28. Mar 2014, 19:51
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Linux Baby! LINUX!

Re: USB Devicea - Failed to Attach device

Postby socratis » 2. Dec 2017, 11:59

  1. It took me a while to figure out what "winpuke, "winturd" and "winslobber" meant. I don't use Windows either, but I don't enter in a discussion with such a negative attitude. Especially when asking for help.
  2. You copied my signature but you completely reverted its message. To mock me? You didn't have that signature when we started the discussion, that's for sure.
  3. You didn't actually read carefully the article I linked you to, or you don't know how to follow instructions. And you deemed it not helpful while trying to justify your inability to comprehend a series of generic instructions. I guess you wanted the FAQ to be written specifically for your Dell.
For these reasons, I'm done helping you, I'll let someone else do it. Either that or when and if you change your attitude, we could possibly talk again. Good luck with your virtualization project.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 12648
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: USB Devicea - Failed to Attach device

Postby WeManageIT » 5. Dec 2017, 02:54

For those following along at home, and like to get complete answers like me.

USB DRIVERS FOR winpuker 7 guests:

http://www.dell.com/support/home/us/en/ ... erId=DN16M

Installed and works.

Tested with my Seagate Drive in both front and rear ports of the host.

So maybe some one can add this to a wiki, or FAQ, or HOWTO some place, so others will have the info at hand.
Do NOT reply with the "POST REPLY" button, please use "QUOTE", on the post.
WeManageIT
 
Posts: 7
Joined: 28. Mar 2014, 19:51
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: Linux Baby! LINUX!

Re: USB Devicea - Failed to Attach device

Postby socratis » 5. Dec 2017, 03:03

For all of those that read the above message:

You do NOT have to download the Dell drivers. Your Virtual Machine is NOT a Dell computer.

You need to download the generic USB3 Intel drivers, something that is spelled *clearly* in the FAQ. Do not experiment and do not follow unsubstantiated advice.

@WeManageIT
I'd really appreciate it if you didn't spread misinformation.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 12648
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5


Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: Google [Bot], Yahoo [Bot] and 23 guests