USB Disk problem on ESXi 6

[sorry4uboth]

Hello everyone

I have installed an ESXi on a server of mine to test and use it as experience.

I had a USB Disk connected to it and was using it as datastore and everything was fine, until I did something stupid and removed it while it was connected.

so it happens now that the ESXi does not detect any usb disks now as a datastore.

I've searched and check all possible commands to fix the issue but nothing so far.

lsusb returns "Bus 001 Device 003: ID 1840:13fd" as this is the USB disk

also I have these in vmkernel log while I use above command:

2017-07-24T10:56:53.539Z cpu17:42528)<6>usb usb2: resumed

2017-07-24T10:56:53.604Z cpu17:42528)<6>usb 2-1: resumed

2017-07-24T10:56:53.670Z cpu17:42528)<6>usb 2-1.3: resumed

2017-07-24T10:56:53.725Z cpu17:42528)<6>usb usb3: resumed

2017-07-24T10:56:54.730Z cpu13:33237)<4>uhci_hcd 0000:01:00.4: Controller not stopped yet!

2017-07-24T10:56:56.218Z cpu13:33259)<6>usb usb3: suspended

2017-07-24T10:56:56.245Z cpu4:33257)<6>usb 2-1.3: suspended

2017-07-24T10:56:58.629Z cpu3:33243)<6>usb 2-1: suspended

2017-07-24T10:57:01.370Z cpu12:33259)<6>usb usb2: suspended

I have this error in my logs while I try to restart usbarbitrator service:

2017-07-24T11:04:58Z usbarb[43275]: VMware USB Arbitration Service Version 13.1.14

2017-07-24T11:04:58Z usbarb[43275]: USBArb: Attempting to connect to existing arbitrator on /var/run/vmware/usbarbitrator-socket.

2017-07-24T11:04:58Z usbarb[43275]: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2017-07-24T11:04:58Z usbarb[43275]: SOCKET connect failed, error 2: No such file or directory

2017-07-24T11:04:58Z usbarb[43275]: USBArb: Failed to connect to the existing arbitrator.

2017-07-24T11:06:32.806Z cpu12:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:32.864Z cpu13:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:32.918Z cpu13:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:32.971Z cpu22:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.018Z cpu23:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.065Z cpu23:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.090Z cpu23:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.130Z cpu23:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.164Z cpu23:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.216Z cpu23:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.263Z cpu16:43376)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.309Z cpu17:43376)FSS: 5338: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': No filesystem on the device

2017-07-24T11:06:33.430Z cpu12:43376)VC: 3551: Device rescan time 147 msec (total number of devices 6)

2017-07-24T11:06:33.430Z cpu12:43376)VC: 3554: Filesystem probe time 464 msec (devices probed 4 of 6)

2017-07-24T11:06:33.430Z cpu12:43376)VC: 3556: Refresh open volume time 47 msec

2017-07-24T11:06:33.648Z cpu13:43380)<6>usb passthrough enabled; all eligible devices will be unclaimed by kernel drivers

2017-07-24T11:06:33.788Z cpu0:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.852Z cpu0:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.898Z cpu0:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.926Z cpu4:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:33.968Z cpu4:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:34.020Z cpu8:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:34.044Z cpu10:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:34.095Z cpu10:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:34.140Z cpu0:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:34.193Z cpu10:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:34.250Z cpu10:43382)<3>ata2.00: bad CDB len=16, scsi_op=0x9e, max=12

2017-07-24T11:06:34.291Z cpu10:43382)FSS: 5338: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': No filesystem on the device

2017-07-24T11:06:34.365Z cpu0:43382)VC: 3551: Device rescan time 95 msec (total number of devices 6)

2017-07-24T11:06:34.365Z cpu0:43382)VC: 3554: Filesystem probe time 409 msec (devices probed 4 of 6)

2017-07-24T11:06:34.365Z cpu0:43382)VC: 3556: Refresh open volume time 72 msec

2017-07-24T11:06:34.627Z cpu16:33049)ScsiUid: 273: Path 'vmhba32:C0:T0:L0' does not support VPD Device Id page.

2017-07-24T11:06:34.629Z cpu13:33049)VMWARE SCSI Id: Could not get disk id for vmhba32:C0:T0:L0

any kind of tip/help/suggestion is appreciated.

Best,

[tulsianandg]

Hi..

Please ensure that the USB devices are supported, please refer to KB: 1021345

To resolve the issue, restart the usbarbitrator service.

1>Run this command to stop the usbarbitrator service:

/etc/init.d/usbarbitrator stop

2>Disconnect and reconnect the USB key or disk device media. The device is automatically mounted under /vmfs/volumes/NO NAME/.

After using the device, start the usbarbitrator service by running this command:

/etc/init.d/usbarbitrator start

Please let me know if this resolves the issue.

[dekoshal]

SSH to esxi host.

1. Run command  CD /vmfs/devices/disks

2. Identify USB disk ID

3. Run Command partedUtil getptbl /vmfs/devices/disks/<DeviceID>

4. Run Command  partedUtil getUsableSectors /vmfs/devices/disks/<DeviceID>

5.Share output here

If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points.

Best Regards,

Deepak Koshal

CNE|CLA|CWMA|VCP4|VCP5|CCAH