Skip to main content

Mounting ISO from ILO/iDRAC of an ESXi host

 

Symptoms
Does not detect the ISO.
Purpose
To mount an ISO from ILO/iDRAC to ESXi host.
Cause
Unknown
Workaround
  •  Run below command and see if you can find any USB vmhba
esxcfg-mpath -l

For eg.,
usb.vmhba32-usb.0:0-eui.00e04c2020202000
   Runtime Name: vmhba32:C0:T0:L0
   Device: eui.00e04c2020202000
   Device Display Name: Local USB Direct-Access (eui.00e04c2020202000)
   Adapter: vmhba32 Channel: 0 Target: 0 LUN: 0
   Adapter Identifier: usb.vmhba32
   Target Identifier: usb.0:0
   Plugin: NMP
   State: active
   Transport: usb
usb.vmhba33-usb.0:0-
   Runtime Name: vmhba33:C0:T0:L0
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba33 Channel: 0 Target: 0 LUN: 0
   Adapter Identifier: usb.vmhba33
   Target Identifier: usb.0:0
   Plugin: NMP
   State: active
   Transport: usb

   
  • The USB vmhba  showing "No associated device" is the virtual USB / USB cd-rom where ISO has been mounted from iLO/iDRAC.
  •  Run below command to load the iso9660 module.
vmkload_mod iso9660
  • Run below command and you should be able to see an attached device/path for the ISO on USB vmhba.
esxcfg-mpath -l

For eg.,


usb.vmhba32-usb.0:0-eui.00e04c2020202000
   Runtime Name: vmhba32:C0:T0:L0
   Device: eui.00e04c2020202000
   Device Display Name: Local USB Direct-Access (eui.00e04c2020202000)
   Adapter: vmhba32 Channel: 0 Target: 0 LUN: 0
   Adapter Identifier: usb.vmhba32
   Target Identifier: usb.0:0
   Plugin: NMP
   State: active
   Transport: usb
usb.vmhba33-usb.0:0-mpx.vmhba33:C0:T0:L0
   Runtime Name: vmhba33:C0:T0:L0
   Device: mpx.vmhba33:C0:T0:L0
   Device Display Name: Local USB Direct-Access (mpx.vmhba33:C0:T0:L0)
   Adapter: vmhba33 Channel: 0 Target: 0 LUN: 0
   Adapter Identifier: usb.vmhba33
   Target Identifier: usb.0:0
   Plugin: NMP
   State: active
   Transport: usb
  •  To mount the ISO to the host run below command.
vsish -e set /vmkModules/iso9660/mount mpx.vmhba33:C0:T0:L0
  • After that you should see a new datastore showing the ISO contents and you should be able to browse to that datastore.
ls -l /vmfs/volumes/
cd /vmfs/volumes/<datastore_name>
  • If you want to unmount the ISO, please run below command.
vsish -e set /vmkModules/iso9660/umount mpx.vmhba33:C0:T0:L0
  • To unload the iso9660 module.
vmkload_mod -u iso9660

Note- Please make sure the ISO is mounted at iLO/iDRAC and is visible in BIOS before proceeding with the above steps.

Comments

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...