Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

NSX-T VIBs fail to install/upgrade, due to insufficient space in bootbank on ESXi host. (74864)

Last Updated: 3/7/2024Categories: TroubleshootingTotal Views: 54314Language:
JapaneseEnglish

24 like this article

Subscribe to get an email
newsletter with new updates

24 people found this helpful Please provide article feedback:

Symptoms

ESXi 6.7

When attempting to install NSX-T on ESXi host, it may fail.

ESXi host logs (esxupdate.log) display message(s) similar to:

20**-**-**T13:37:50Z esxupdate: 5557508: BootBankInstaller.pyc: ERROR: The pending transaction requires 245 MB free space, however the maximum supported size is 239 MB.^@

Cause

This issue occurs when the bootbank / altbootbank runs out of space on the ESXi host.  There is no supported procedure to increase the size of either bootbank on the ESXi host.

Some ESXi images provided by third-party vendors may include VIBs which are not in use and can be relatively large in size. This can result in insufficient space in bootbank/alt-bootbank when installing/upgrading any VIBs.

Resolution

This issue is resolved in ESXi 7.0 which introduced a larger bootbank for both upgraded and newly installed ESXi hosts.

Workaround

To work around this issue, free the additional space on the bootbank by un-installing non-required VIBs on the ESXi host using the 'esxcli software vib remove -n <vib-name>' command.

1) Check the free space in bootbank / altbootbank:

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

2) Check which partition (bootbank or altbootbank) contain the VIBs last updated by running the below commands:

grep updated /bootbank/boot.cfg
updated=8

grep updated /altbootbank/boot.cfg
updated=7

If bootbank has the higher value for “updated”, as in the example above,  then that partition has the latest update to the VIBs. Otherwise altbootbank would have the latest update to the VIBs.

3) NSX software space requirements, note reduced sizing from 3.0

NSX-T 2.4.0 - VMware ESXi 6.5 - 32.17 MB
NSX-T 2.4.0 - VMware ESXi 6.7 - 32.55 MB
NSX-T 2.5.0 - VMware ESXi 6.5 - 37.24 MB
NSX-T 2.5.0 - VMware ESXi 6.7 - 37.64 MB
NSX-T 3.0.0 - VMware ESXi 6.5 - 29.16 MB
NSX-T 3.0.0 - VMware ESXi 6.7 - 29.42 MB
NSX-T 3.0.0 - VMware ESXi 7.0 - 29.43 MB

As well as this space requirement for the NSX VIBs, ESX install/upgrade framework has the following requirements:
For an NSX-T upgrade, an additional 20MB free space buffer is required in the partition with the highest updated value (check step 2 above to find the partition with highest updated value).
For a new install of NSX-T, an additional 10MB free space buffer is required in the partition with highest updated value.

4) To determine the currently installed VIBs in bootbank/altbootbank partitions run the following command:

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Downloading and Installing the standalone VMware Remote Console (VMRC) in vSphere (2091284)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant