cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
trajectory
Ctrl-Alt-Del
Posts: 12
Registered: ‎12-23-2015
Location: US
Views: 495
Message 1 of 2

M710q tiny + Drobo 5C + ESXi

A Drobo 5C DAS connected to a Lenovo M710q host will only show up as bcdUSB 2.10 high speed rather than 3.0 superspeed.  ESXi was initially VMware-ESXi-6.5.0.update02-8294253-LNV-20180605 and later updated to 6.7 from vmware's repository as part of troubleshooting.  ntfs throughput for the Drobo added as a device in a Server 2012 vm via usb 3.0 controller in the vm settings reaches only ~40MB/s.   Reverting to xhci in place of the newer vmkusb using https://kb.vmware.com/s/article/2147650 has been tried and  module status was verified to confirm it did change to xhci but it still stayed at 2.10 with no change other than xhci throughput being somewhat slower than vmkusb.  Different usb cable has been tried.  Differnt usb ports on front & rear with the "SS" label have been tried. Bios has been updated.  A sandisk usb 3.0 memory stick plugged into another M710q on ESXi 6.7 does populate as usb 3.0.   An older model Drobo 5D connected to Lenovo M73 tiny or M83 tiny running ESXi 6.0 populates at usb 3.0 and reaches ~250MB/s ntfs throughput when added as a usb device in a Server 2012 vm via xhci controller in the vm settings.   Not a 1:1 comparison but it's the closest matching setup I have access to right now.  Key lines in the output below are the bcdUSB entries under the Data Robotics sections.  Any suggestions to get 3.0 out of this setup are appreciated.

 

 

 BIOS Info: #0
    Vendor: "LENOVO"
    Version: "M1AKT3BA"
    Date: "09/18/2018"

System Info: #1
    Manufacturer: "LENOVO"
    Product: "10MR0004US"
    Version: "ThinkCentre M710q"

 

Drobo 5C, Lenovo M710q 10MR0004US with intel B250 chipset, ESXi 6.7.0 build-9484548:

    lsusb -v  
      
    Bus 001 Device 003: ID 19b9:3443 Data Robotics   
    Device Descriptor:  
      bLength                18  
      bDescriptorType         1  
      bcdUSB               2.10  
      bDeviceClass            0 (Defined at Interface level)  
      bDeviceSubClass         0   
      bDeviceProtocol         0   
      bMaxPacketSize0        64  
      idVendor           0x19b9 Data Robotics  
      idProduct          0x3443   
      bcdDevice            0.00  
      iManufacturer           1 Drobo  
      iProduct                2 Drobo5C  
 

 

 

Drobo 5D, Lenovo M73 10AY001YUS with Intel H81 Express Chipset, ESXi 6.0.0 build-7504637 for comparison:

    lsusb -v  
      
    Bus 004 Device 002: ID 19b9:3444 Data Robotics   
    Device Descriptor:  
      bLength                18  
      bDescriptorType         1  
      bcdUSB               3.00  
      bDeviceClass            0 (Defined at Interface level)  
      bDeviceSubClass         0   
      bDeviceProtocol         0   
      bMaxPacketSize0         9  
      idVendor           0x19b9 Data Robotics  
      idProduct          0x3444   
      bcdDevice            0.00  
      iManufacturer           1 Drobo  
      iProduct                2 Drobo5D  

 

 

 

booted with the default esxcli system module set -m=vmkusb -e=TRUE:

 
    [root@localhost:~] lsusb  
    Bus 001 Device 003: ID 19b9:3443 Data Robotics  
    Bus 001 Device 002: ID 8087:0a2b Intel Corp.  
    Bus 001 Device 001: ID 0e0f:8003 VMware, Inc.  
      
    [root@localhost:~] esxcli system module list | grep -i xhci  
    [root@localhost:~] esxcli system module list | grep -i usb  
    vmkusb                              true        true  
      
    [root@localhost:~] lsusb -v | less  
    Bus 001 Device 003: ID 19b9:3443 Data Robotics  
    Device Descriptor:  
      bLength                18  
      bDescriptorType         1  
      bcdUSB               2.10  

 

 

booted with alternate esxcli system module set -m=vmkusb -e=FALSE:

 
    [root@localhost:~] esxcli system module list | grep -i xhci  
    xhci                                true        true  
    [root@localhost:~] esxcli system module list | grep -i usb  
    usb                                 true        true  
    usb-storage                         true        true  
    usbnet                              true        true  
    vmkusb                             false       false  
      
    [root@localhost:~] lsusb  
    Bus 001 Device 003: ID 19b9:3443 Data Robotics  
    Bus 001 Device 002: ID 8087:0a2b Intel Corp.  
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub  
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  
      
    [root@localhost:~] lsusb -v   
    Bus 001 Device 003: ID 19b9:3443 Data Robotics  
    Device Descriptor:  
      bLength                18  
      bDescriptorType         1  
      bcdUSB               2.10  

 

this was the only mention of xhci (usb 3.0) i located in the bios settings:

001.png

 

Highlighted
trajectory
Ctrl-Alt-Del
Posts: 12
Registered: ‎12-23-2015
Location: US
Views: 454
Message 2 of 2

Re: M710q tiny + Drobo 5C + ESXi

if anyone else comes across this in the future,  shutting down the drobo, reconnecting the USB-C connector in the opposite direction, and powering it back up has resolved the problem and it is now connected at USB 3.0.  The orientation of this connector should technically not matter since it's symmetrical and I had no expectation this would work but in this specific setup with unsupported hardware & OS it apparently clears up an unknown issue.

Check out current deals!


Shop current deals

Top Kudoed Authors