VMware Cloud Community
yeowkm2809
Contributor
Contributor

installation error when updating ESXi 6.5

i am trying to update one of my ESXi host from 6.5 update 1 ESXi-6.5.0-20171204001-standard to ESXi-6.5.0-20190304001-standard and it encountered the following error message

[InstallationError]

[Errno 28] No space left on device

       vibs = VMware_locker_tools-light_6.5.0-2.71.10868328

Please refer to the log file for more details.

reboot the host and it stays at 6.5.0 update 1.

my server is a Dell R720.

any one encounter the same error before?

i update using the esxcli command

0 Kudos
4 Replies
Emanakhly
Contributor
Contributor

I faced this issue before , and i did the following and my issue disappear

First step is to Install the locker vib manually

cd /tmp

wget http://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/tools-light/VMware_locker_to...

esxcli software vib install -f -v /tmp/VMware_locker_tools-light_6.5.0-0.23.5969300.vib

Second step is to update

esxcli software profile update -f -p ESXi-6.5.0-20170702001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-

depot-index.xml

then reboot .

the following links could help also :

VMware Knowledge Base

How to update any VMware ESXi Hypervisor to the latest using ESXCLI for easy download and install | ...

0 Kudos
ashishsingh1508
Enthusiast
Enthusiast

If it says no space, you can try above method plus remove any unused VIBs and reboot the host.

Try installing again.

Ashish Singh VCP-6.5, VCP-NV 6, VCIX-6,VCIX-6.5, vCAP-DCV, vCAP-DCD
0 Kudos
IRIX201110141
Champion
Champion

There is a much easier way to solve that problem. The good thing is youre not the first one which that kind of problem Smiley Happy

2 Solutions exists:

1. Add swap space on a existing datastore

2. Remove the *.vib

I preferer method #1. Take a look to https://www.eknori.de/2018-03-18/vmware-esxi-errno-28-no-space-left-on-device-ibmchampion/

Regards

Joerg

0 Kudos
JacobDEvans
Enthusiast
Enthusiast

# Assumption - datastore1 is your primary/default datastore.

Run these two commands:

esxcli sched swap system set -d True

esxcli sched swap system set -n datastore1

Then proceed with update.

CLI Source: https://code.vmware.com/docs/4164/vsphere-command-line-interface-reference#/doc/esxcli_sched.html

0 Kudos