When you use vCenter 5.5 to management Esxi 5.1 ,you will have error
“Unable to install VMware Tools. An error occurred while trying to access image file “/usr/lib/vmware/isoimages/windows.iso” needed to install VMware Tools: 2 (No such file or directory). If your product shipped with the VMware Tools package, reinstall VMware ESX, then try again to install the VMware Tools package in the virtual machine. The required VMware Tools ISO image does not exist or is inaccessible.”
Further investigation through remote tech support into the ESXi host I found that the iso image is missing from the directory and the directory is 100% full, which must be the reason for not installing the tool images. I found that old tool images are not removed from the system and as a result while upgrading , its not able to copy the new images due to file system full.
You need to copy .iso, .sig and tools-key.pub. files, because all these files required if you want to upgrade the vmware tools.From /5.5.0/vmtools folder to /5.1.0/vmtools folder.
Example: file need for install VMware tool to window os.
1) Start the remote tech support (SSH), Click on the ESXi host on the left panel, go to configuration ,
on the software section click on Security profile, Click properties on the right top corner, click remote
tech support and click option and start the ssh.
2)User puty to SSH to ESXi host.
/vmfs/volumes/526a8fe2-729bdd42-e8a5-6805ca10322b/packages/5.5.0/vmtools # cp window.* wi
—————————–Consult form http://sjmeyers.blogspot.com—————————————————
Unable to install VMware Tools
Unable to install VMware Tools. An error occurred while trying to access image file “/usr/lib/vmware/isoimages/windows.iso” needed to install VMware Tools: 2 (No such file or directory). If your product shipped with the VMware Tools package, reinstall VMware ESX, then try again to install the VMware Tools package in the virtual machine. The required VMware Tools ISO image does not exist or is inaccessible.
Troubleshooting SSH to the Vmware host reveals that the /usr/lib/vmware is not accessible
/vmfs/volumes is missing Hypervisor3
The ESXi partition table can be checked using the command fdisk -l
There is a Warning for partition table 8 Warning: ignoring extra data in partition table 8
And the file system for mpx.vmhba32:C0:T0:L0p8 is Unknowm /dev/disks/mpx.vmhba32:C0:T0:L0p8 ? 740786 1480957 757935405 5a Unknown
mpx.vmhba32:C0:T0:L0p8 should be the scratch disk location.
It is recommended that the persistent scratch location be set for ESXi
Configuring persistent scratch location using the vSphere Client
You can configure persistent scratch space for ESXi using the vSphere Client:
- Connect to vCenter Server or the ESXi host using the vSphere Client.
- Select the ESXi host in the inventory.
- Click the Configuration tab.
- Click Storage.
- Right-click a datastore and select Browse.
- Create a uniquely-named directory for this ESX host (eg,
- Close the Datastore Browser.
- Click Advanced Settings under Software.
- Select the ScratchConfig section.
- Change the
ScratchConfig.ConfiguredScratchLocationconfiguration option, specifying the full path to the directory. For example:
- Click OK.
- Put the ESXi host in maintenance mode and reboot for the configuration change to take effect.
Recreating scratch files including Vmware tools iso’s.
Once the scratch location has been set you can run the current ESXi 4.1 update 2 patch this will recreate the Vmware tools installation iso in the scratch file location.
Once the patch has applied reboot the host.
You can check that the vmtools iso’s have been created by browsing the persistent scratch datastore.
You will then be able to deploy Vmware tools
cd / #this command changes directory to root
cp -R locker/ locker.old/ #this command copies the folder locker/ to locker.old/ recursively
rm -rf locker/ #this command removes the directory and contents of locker/
ln -s store/ locker #this command creates a symbolic link of store/ (the target) to locker/ (link)
Note: To SSH into host, you need to enable SSH which is disabled by default. After enabling SSH you will see a warning status on your host in vSphere with NO ALARM. This is simply just saying this host is more ‘vulnerable’ because SSH is turned on (which is strictly considered a troubleshooting tool). To turn SSH on, log into ESXi on your host using a local terminal to your server and go to “Troubleshooting Options” and enable SSH. Remember to disable SSH to get rid of the warning icon on your host in vSphere.