Jmicron USB Hard Drive Caddy Will Not Connect to Guest

Discussions about using Linux guests in VirtualBox.
Post Reply
JaDy99
Posts: 1
Joined: 7. Jul 2021, 13:47

Jmicron USB Hard Drive Caddy Will Not Connect to Guest

Post by JaDy99 »

Virtual Box Version: 6.1.22 r144080 (Qt5.6.2)
Virtual Box Guest Additions: Installed on guest
Host OS: Windows 10 (64-bit) 21H1, 64GB RAM
Guest OS: Ubuntu 20.04 (64-bit), 4GB RAM, 5.8.0-59-generic Kernel

Hi,
I am having trouble getting a HDD to connect to my Ubuntu VirtualBox VM through a StarTech Jmicron USB 3.0 Caddy.
The HDD is recognised on the host, and when I attempt to attach it to the guest, it appears to do nothing and it remains accessible to the host. Virtual Box will then create a duplicate caddy entry in the listed USB devices for the VM.
So, I read through the USB trouble shooting topic on the forums and applied the USB filter for the caddy. This resulted in a big hit to performance on my guest and I realised that the caddy was being seen by the guest OS, but would not be connected. However, as it was applied by a filter, this process was just repeating over and over again, stalling the VM. At this point I viewed the Ubuntu logs as saw that it would not connect the Caddy due to UAS driver support, one cycle of this log can be seen below, this was repeated infinitely until I unplugged the caddy.
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.858161] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.880373] usb 2-1: unable to get BOS descriptor or descriptor too short
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.883672] usb 2-1: string descriptor 0 read error: -32
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.883679] usb 2-1: New USB device found, idVendor=152d, idProduct=0561, bcdDevice= 2.07
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.883683] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jul 7 08:58:23 SIFTvm-Validation mtp-probe: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:0c.0/usb2/2-1"
Jul 7 08:58:23 SIFTvm-Validation mtp-probe: bus: 2, device: 2 was not an MTP device
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.936753] usb 2-1: USB controller 0000:00:0c.0 does not support streams, which are required by the UAS driver.
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.936754] usb 2-1: Please try an other USB controller if you wish to use UAS.
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.936754] usb-storage 2-1:1.0: USB Mass Storage device detected
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.938820] scsi host3: usb-storage 2-1:1.0
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.939040] usbcore: registered new interface driver usb-storage
Jul 7 08:58:23 SIFTvm-Validation kernel: [ 122.946622] usbcore: registered new interface driver uas
Jul 7 08:58:23 SIFTvm-Validation mtp-probe: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:0c.0/usb2/2-1"
Jul 7 08:58:23 SIFTvm-Validation mtp-probe: bus: 2, device: 2 was not an MTP device
Jul 7 08:58:25 SIFTvm-Validation kernel: [ 123.281842] usb 2-1: USB disconnect, device number 2
However, with the same caddy and the same HDD, it will connect to an identical Ubuntu 20 host machine and it will connect to an identical Ubuntu 20 VM virtualised with VMware. I have searched through many forums on this and have tried blacklisting the UAS driver, but I got no success. Because the caddy works with an identical build of Ubuntu on different platforms, I cannot see how it can be to do with the Ubuntu install or an issue with the hardware. Also, when I use the same HDD with a StarTech ASMedia USB 3.0 Caddy, the drive is mounted in the same VBox VM perfectly as expected, even without a filter.

I hope somebody can help I do not know where else to look next.
Thanks in advance for your help.
Attachments
USB_Basics_Asking_for_Help.log
Host commands requested from USB basics and troubleshooting forum.
(9.22 KiB) Downloaded 9 times
Virtual Machine Log Files.zip
Contains three VBox log files.
- One for operation without a USB filter.
- One for operation with a USB filter, showing the infinite loop of Caddy not connecting due to UAS Driver.
- One for operation with a USB filter and blacklisted UAS driver which still produces infinite loop.
(85.07 KiB) Downloaded 7 times
Post Reply