VMware Cloud Community
EborComputing
Contributor
Contributor

USB devices is not mounted in VMware vSphere Hypervisor 5

Hi All,

I have been trying in vain to get an 8GB Kingston USB  pen formated in Fat32 to be mounted in ESXi.

I have turned off the USB arbitration service and unplugged and then replugged the USB device.

lsusb lists the USB as follows:

Bus 01 Device 04: ID 0951:1613 Kingston Technology DataTraveler 8GB Pen Drive

ls -al /vmfs/devices/disks lists the USB as well::

-rw-------    1 root     root         8017412096 Feb 29 15:51 mpx.vmhba38:C0:T0:L0
-rw-------    1 root     root         8015314944 Feb 29 15:51 mpx.vmhba38:C0:T0:L0:1

However, it does not exist in /vmfs/volumes as "No Name"

running esxcfg-mpath -l returns the following:

usb.vmhba38-usb.0:0-mpx.vmhba38:C0:T0:L0
   Runtime Name: vmhba38:C0:T0:L0
   Device: mpx.vmhba38:C0:T0:L0
   Device Display Name: Local USB Direct-Access (mpx.vmhba38:C0:T0:L0)
   Adapter: vmhba38 Channel: 0 Target: 0 LUN: 0
   Adapter Identifier: usb.vmhba38
   Target Identifier: usb.0:0
   Plugin: NMP
   State: active
   Transport: usb

Is this a known problem and is there a work-around?

Also, I cannot seem to access the CD-ROM as well. esxcfg-mpath -l returns:

sata.vmhba0-sata.0:0-mpx.vmhba0:C0:T0:L0
   Runtime Name: vmhba0:C0:T0:L0
   Device: mpx.vmhba0:C0:T0:L0
   Device Display Name: Local TEAC CD-ROM (mpx.vmhba0:C0:T0:L0)
   Adapter: vmhba0 Channel: 0 Target: 0 LUN: 0
   Adapter Identifier: sata.vmhba0
   Target Identifier: sata.0:0
   Plugin: NMP
   State: active
   Transport: sata

I load the iso9669 module but when I run /sbin/vsish -e set /vmkModules/iso9660/mount mpx.vmhba0:C0:T0:L0  I get the following error:

VSISHCmdSet():Set failed: Not supported
Error: Error in command set: Not supported

I read here (http://communities.vmware.com/message/1698234) that you have to set usb mode in BIOS to USB 1.1. Is this correct?

Thanks in advance,

Vlad

Tags (4)
0 Kudos
8 Replies
VMmatty
Virtuoso
Virtuoso

Moved to ESXi 5 forum.

Matt | http://www.thelowercasew.com | @mattliebowitz
0 Kudos
EborComputing
Contributor
Contributor

The CD-ROM problem may be to do with the use of the TEAC DV-28S-V DVD ROM with rev C.0L. I have not been able to find an updated firmware for it from the HP site, only from DELL site. Don't know if it is safe to use the one from DELL.

0 Kudos
EborComputing
Contributor
Contributor

Hi All,

I am still having trouble with USB access. Note this is on the free VMware vSphere Hypervisor 5.0

The usbarbitrator has been stopped and the USB drive re-plugged in.

lsusb returns: Bus 01 Device 04: ID 0951:1613 Kingston Technology DataTraveler 8GB Pen Drive

==================================

esxcfg-mpath -l returns:

usb.vmhba38-usb.0:0-mpx.vmhba38:C0:T0:L0
   Runtime Name: vmhba38:C0:T0:L0
   Device: mpx.vmhba38:C0:T0:L0
   Device Display Name: Local USB Direct-Access (mpx.vmhba38:C0:T0:L0)
   Adapter: vmhba38 Channel: 0 Target: 0 LUN: 0
   Adapter Identifier: usb.vmhba38
   Target Identifier: usb.0:0
   Plugin: NMP
   State: active
   Transport: usb

==================================

esxcfg-scsidevs -l returns:

mpx.vmhba38:C0:T0:L0
   Device Type: Direct-Access
   Size: 7646 MB
   Display Name: Local USB Direct-Access (mpx.vmhba38:C0:T0:L0)
   Multipath Plugin: NMP
   Console Device: /vmfs/devices/disks/mpx.vmhba38:C0:T0:L0
   Devfs Path: /vmfs/devices/disks/mpx.vmhba38:C0:T0:L0
   Vendor: Kingston  Model: DT 101 II         Revis: PMAP
   SCSI Level: 2  Is Pseudo: false Status: on
   Is RDM Capable: false Is Removable: true
   Is Local: true  Is SSD: false
   Other Names:
      vml.0000000000766d68626133383a303a30
   VAAI Status: unsupported

==================================

esxcli storage core path list returns:

usb.vmhba38-usb.0:0-mpx.vmhba38:C0:T0:L0
   UID: usb.vmhba38-usb.0:0-mpx.vmhba38:C0:T0:L0
   Runtime Name: vmhba38:C0:T0:L0
   Device: mpx.vmhba38:C0:T0:L0
   Device Display Name: Local USB Direct-Access (mpx.vmhba38:C0:T0:L0)
   Adapter: vmhba38
   Channel: 0
   Target: 0
   LUN: 0
   Plugin: NMP
   State: active
   Transport: usb
   Adapter Identifier: usb.vmhba38
   Target Identifier: usb.0:0
   Adapter Transport Details: Unavailable or path is unclaimed
   Target Transport Details: Unavailable or path is unclaimed

==================================

esxcli storage core device list returns:

mpx.vmhba38:C0:T0:L0
   Display Name: Local USB Direct-Access (mpx.vmhba38:C0:T0:L0)
   Has Settable Display Name: false
   Size: 7646
   Device Type: Direct-Access
   Multipath Plugin: NMP
   Devfs Path: /vmfs/devices/disks/mpx.vmhba38:C0:T0:L0
   Vendor: Kingston
   Model: DT 101 II
   Revision: PMAP
   SCSI Level: 2
   Is Pseudo: false
   Status: on
   Is RDM Capable: false
   Is Local: true
   Is Removable: true
   Is SSD: false
   Is Offline: false
   Is Perennially Reserved: false
   Thin Provisioning Status: unknown
   Attached Filters:
   VAAI Status: unsupported
   Other UIDs: vml.0000000000766d68626133383a303a30

I tried to use esxcli storage filesystem mount to mount the usb manually but I can't seem to find its UUID or label.

Has anyone got this to work? The sever is standalone so I have to do things via the TSM at the server.

TIA,

Vlad

0 Kudos
krishnaprasad
Hot Shot
Hot Shot

I do face the same issue described here. Any solution found?

Thanks,

Krishnaprasad

0 Kudos
KraL
Enthusiast
Enthusiast

This issue is still there.

Are there anyone around with some light?

0 Kudos
Linjo
Leadership
Leadership

Did you follow the instructions in KB1036340?

Especially this one:

"The USB key or disk device media is formatted with a FAT16 partition and is of maximum size 2GB"

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
KraL
Enthusiast
Enthusiast

Yes, but unfortunately without more luck.

This step was already mentioned on reply 3.

0 Kudos
Linjo
Leadership
Leadership

KraL wrote:

Yes, but unfortunately without more luck.

This step was already mentioned on reply 3.

But in reply 3 its mentioned that an 8GB stick is used, maximum possible is 2GB according to the KB.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos