ls -l ... lrwxrwxrwx 1 root root 49 Aug 9 19:06 altbootbank -> /vmfs/volumes/d7607071-826ffd54-8cd6-69cc3f3840ff drwxr-xr-x 1 root root 512 Aug 9 19:04 bin lrwxrwxrwx 1 root root 49 Aug 9 19:06 bootbank -> /vmfs/volumes/42910973-563a8bff-11f1-af4f22ba2855 ...
To see how much space is used and free:
df -h Filesystem Size Used Available Use% Mounted on VMFS-6 383.8G 125.0G 258.7G 33% /vmfs/volumes/stgb01 vfat 285.8M 172.9M 112.9M 60% /vmfs/volumes/5c669304-eda3d71f-1224-0050560302fa vfat 249.7M 149.6M 100.1M 60% /vmfs/volumes/d7607071-826ffd54-8cd6-69cc3f3840ff -> partitions used for altbootbank, see above vfat 249.7M 150.5M 99.2M 60% /vmfs/volumes/42910973-563a8bff-11f1-af4f22ba2855 -> partitions used for bootbank, see above
grep updated /bootbank/boot.cfg
updated=8
grep updated /altbootbank/boot.cfg
updated=7
ls -lSrh /bootbank/ ls -lSrh /altboobank/
Note: If the ESXi server was installed using a software image provided by a third party, you need to contact the third party and work with them to identify the VIBs which can be safely removed.5) Once the VIBs to be removed have been determined, remove the unused VIBs using command:
esxcli software vib remove -n <vib-name>
If any issues are encountered during the above process, file a support request with VMware support and quote this Knowledge base article (74864) in the problem description.
6) Once the required VIBs have been removed and bootbank / altbootbank has the required space to proceed as indicated in (Step 3), proceed with install or upgrade.