Bootbank partition is where the ESXi hypervisor resides then, just a couple of questions.
Is this host installed in a SDCard or a LUN?
Did you check via SSH if there is space in the local or remote disk?
It is installed on the local disc. 160 GB SSD with 75 GB of free space.
Ramdisk Size Used Available Use% Mounted on
root 32M 2M 29M 6% --
etc 28M 184K 27M 0% --
opt 32M 0B 32M 0% --
var 48M 328K 47M 0% --
tmp 256M 8K 255M 0% --
iofilters 32M 0B 32M 0% --
shm 1024M 0B 1024M 0% --
hostdstats 114M 1M 112M 1% --
[root@esxi:~] df -h
Filesystem Size Used Available Use% Mounted on
VMFS-6 160.2G 84.9G 75.4G 53% /vmfs/volumes/datastore1
vfat 285.8M 184.0K 285.6M 0% /vmfs/volumes/5c4b8a8e-494810ce-5e4b-3c0754778af6
vfat 249.7M 141.7M 108.0M 57% /vmfs/volumes/a85ac279-7efaeb8e-c61d-4327c4b63be2
vfat 4.0G 19.2M 4.0G 0% /vmfs/volumes/5c4b8ad6-8424c2a7-9899-3c0754778af6
vfat 249.7M 141.7M 108.0M 57% /vmfs/volumes/0ebf8a7e-444dcc99-633d-4d8b61fbfb29
[root@esxi:~] esxcli software profile update -p ESXi-6.7.0-20181002001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
[Errno 28] No space left on device
vibs = VMware_locker_tools-light_10.3.2.9925305-10176879
Please refer to the log file for more details.
(I enabled the swap on datastore1. No clue why the above problem is happening)
I helped myself:
1) Extracted VMware_locker_tools-light_10.3.2.9925305-10176879.vib from update-from-esxi6.7-6.7_update01.zip
2) Copied VMware_locker_tools-light_10.3.2.9925305-10176879.vib to the datastore
3) Installed VMware_locker_tools-light_10.3.2.9925305-10176879.vib via frontend
4) Installed update package via:
esxcli software profile update -p ESXi-6.7.0-20181002001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot
=> Got: "The update completed successfully"
I am in a similar boat -- I am trying to upgrade from 6.7U1 to 6.7U2.
Can you please tell me where you got the zip file from? When I go to the downloads section in myvmware, it's not allowing me to download any 6.7U2 binaries.
I am using a standalone ESXi server with a free license for home use.
use "install" instead of "update". Also put double quotes around the file path like this:
esxcli software vib install -d "/vmfs/volumes/datastore1/update-from-esxi6.7-6.7_update01.zip"
Refer to this for more info: VMware Knowledge Base
Not sure if you are replying to me or not, but where do you download this file from
I found the update files on https://my.vmware.com/group/vmware/patch#search
and then used esxcli software install -d "vmfs/volumes/datastore/isos/update-from-esxi6.7-6.7_update02.zip"
which then successfully upgraded my version. I didn't have to extract the vmware_locker_tools_light as indicated in the original answer.
Yes u are right. I had this issue many times and I always use install instead of update. Be aware that install command might remove third-party packages from host if there are packages install. As long as you don't have any third-party package installed on the ESXi host, install command will be fine.
Using the install command overwrites the existing packages in the system with contents of the patch you are installing, including installing new packages and removing old packages. The installcommand may downgrade packages on the system and should be used with caution. If required, the install command can be used to downgrade a system (only for image profiles) when the --allow-downgrade flag is set.
I am just starting with ESXi and so I didn't have any third-party packages installed. But yes, it's good to know that the install command would overwrite the third-party packages.
However, it's still strange that we get out of space errors -- even when I had more than a TB of space available in the datastore. Not sure if there is a fix for that, other than what the OP suggested of extracting the vib and manually installing it before doing the upgrade.