VMware Cloud Community
paulsamkpz
Enthusiast
Enthusiast
Jump to solution

Failing while doing Esx 6.5 patch update via cli.

[root@localhost:~]  esxcli software vib update -d /vmfs/volumes/paul\/ESXi650-201712001.zip

[StatelessError]

The transaction is not supported: VIB VMW_bootbank_nmlx4-core_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMW_bootbank_nmlx4-rdma_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMware_bootbank_esx-tboot_6.5.0-1.36.7388607 cannot be live installed. VIB VMW_bootbank_nmlx4-en_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMW_bootbank_ntg3_4.1.3.0-1vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_misc-drivers_6.5.0-1.36.7388607 cannot be live installed. VIB VMW_bootbank_nvme_1.2.0.32-5vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_vmkusb_0.1-1vmw.650.1.36.7388607 cannot be live installed. VIB VMware_bootbank_esx-base_6.5.0-1.36.7388607 cannot be live installed. VIB VMware_bootbank_vsan_6.5.0-1.36.7388608 cannot be live installed. VIB VMW_bootbank_nvmxnet3_2.0.0.23-1vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_igbn_0.1.0.0-15vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_vmkata_0.1-1vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_scsi-mpt2sas_19.00.00.00-1vmw.650.0.0.4564106 cannot be live installed. VIB VMW_bootbank_ntg3_4.1.2.0-1vmw.650.1.26.5969303 cannot be removed live. VIB MEL_bootbank_nmlx4-en_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live. VIB VMware_bootbank_vsan_6.5.0-1.26.5912915 cannot be removed live. VIB VMware_bootbank_esx-base_6.5.0-1.26.5969303 cannot be removed live. VIB VMware_bootbank_esx-dvfilter-generic-fastpath_6.5.0-1.26.5969303 cannot be removed live. VIB VMware_bootbank_esx-tboot_6.5.0-1.26.5969303 cannot be removed live. VIB VMW_bootbank_igbn_0.1.0.0-14vmw.650.1.26.5969303 cannot be removed live. VIB MEL_bootbank_nmlx4-core_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live. VIB VMW_bootbank_misc-drivers_6.5.0-1.26.5969303 cannot be removed live. VIB VMW_bootbank_nvmxnet3_2.0.0.22-1vmw.650.1.26.5969303 cannot be removed live. VIB VMW_bootbank_nvme_1.2.0.32-4vmw.650.1.26.5969303 cannot be removed live. VIB Avago_bootbank_scsi-mpt2sas_15.10.07.00-1OEM.550.0.0.1331820 cannot be removed live. VIB MEL_bootbank_nmlx4-rdma_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live.

Please refer to the log file for more details.

1 Solution

Accepted Solutions
paulsamkpz
Enthusiast
Enthusiast
Jump to solution

Hi Guys,

problem was my Esxi OS volume had only 2gb space, which was not sufficient to do an update on it.

Solution : Vmware recommends a minimum of 20 GB OS volume space for Esxi host. Smiley Happy Smiley Happy

View solution in original post

9 Replies
admin
Immortal
Immortal
Jump to solution

if you have esxi install on  USB.

is boot usb disk is full ? vmware will not have enough space to complete the install in the alternate book bank .

Reply
0 Kudos
Twister5800
Contributor
Contributor
Jump to solution

Hi,

Are you using flash media for ESXi, then maybe you need to set swap directory, have a look here:

https://martinsblog.dk/vmware-cannot-update-host-with-esxcli-due-to-error-oserror-errno-28-no-space-...

Also can you post esxupdate log file?

best regards

Martin

Best regards Martin 🙂
Reply
0 Kudos
paulsamkpz
Enthusiast
Enthusiast
Jump to solution

I am using an ISCSI disk device, which is connected via network.

I tried swap directory, that didnt help too.

esxupdate.log

2018-01-24T10:37:56Z esxupdate: 88174: LiveImageInstaller: DEBUG: The transaction is not supported for live install: ['VIB VMware_bootbank_vsan_6.5.0-1.38.7395176 cannot be liv

2018-01-24T10:37:56Z esxupdate: ve installed.', 'VIB VMW_bootbank_nmlx4-en_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed.', 'VIB VMW_bootbank_vmkata_0.1-1vmw.650.1.36.

2018-01-24T10:37:56Z esxupdate: .', 'VIB VMW_bootbank_ntg3_4.1.2.0-1vmw.650.1.26.5969303 cannot be removed live.', 'VIB MEL_bootbank_nmlx4-en_3.15.5.5-1OEM.600.0.0.2768847 cann

2018-01-24T10:37:56Z esxupdate: 88174: HostImage: INFO: LiveImageInstaller is not supported, skipping.^@

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR: Traceback (most recent call last):^@

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 468, in <module>^@

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:     main()^@

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 459, in main^@

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:     ret = CMDTABLE[command](options)^@

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 355, in VibInstallCmd^@

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:     nosigcheck=opts.nosigcheck)^@

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximag

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximag

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximag

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR:   File "/build/mts/release/bora-5969303/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximag

2018-01-24T10:37:56Z esxupdate: 88174: root: ERROR: vmware.esximage.Errors.StatelessError: The transaction is not supported: VIB VMware_bootbank_vsan_6.5.0-1.38.7395176 cannot

2018-01-24T10:37:56Z esxupdate: _bootbank_nmlx4-en_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMW_bootbank_vmkata_0.1-1vmw.650.1.36.7388607 cannot be live inst

2018-01-24T10:37:56Z esxupdate: cannot be removed live. VIB MEL_bootbank_nmlx4-en_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live. VIB VMware_bootbank_esx-dvfilter-generic

Reply
0 Kudos
paulsamkpz
Enthusiast
Enthusiast
Jump to solution

Disk has enough storage Smiley Happy

Reply
0 Kudos
paulsamkpz
Enthusiast
Enthusiast
Jump to solution

Hi Guys,

problem was my Esxi OS volume had only 2gb space, which was not sufficient to do an update on it.

Solution : Vmware recommends a minimum of 20 GB OS volume space for Esxi host. Smiley Happy Smiley Happy

July22
Contributor
Contributor
Jump to solution

I have ESXI 6.5 running from a USB stick (4GB). How did you fix the problem?

For me, I cloned my 4GB to a 32GB, but I'm still seeing the same error. I believe I didn't allow the additional disk space to the correct partition.

Which partition do I need to allow more space? Is it the 2GB bootbank? Or do I need to create a /scratch partition (9)?

-rw-------1 root root    4.0M Aug 13 04:40 mpx.vmhba32:C0:T0:L0:1
-rw-------1 root root    2.0G Aug 13 04:40 mpx.vmhba32:C0:T0:L0:5
-rw-------1 root root    1.9G Aug 13 04:40 mpx.vmhba32:C0:T0:L0:6
-rw-------1 root root  870.0M Aug 13 04:40 mpx.vmhba32:C0:T0:L0:7
-rw-------1 root root   25.4G Aug 13 04:40 mpx.vmhba32:C0:T0:L0:8

I also found a VM KB that suggest setting up a partition scratch partition. I will try this next.

VMware Knowledge Base

Any suggestion is greatly appreciated! Thanks.

Reply
0 Kudos
July22
Contributor
Contributor
Jump to solution

Scratch directory is there but upgrade still fails. Smiley Sad

I see 2 possible issues:

1) 2019-08-13T04:32:39Z esxupdate: 68706: HostImage: ERROR: Failed to send vob install.stage.error: [Errno 27] File too large

2) 2019-08-13T05:52:22Z esxupdate: HostImage: INFO: Installer <class 'vmware.esximage.Installer.BootBankInstaller.BootBankInstaller'> was not initiated - reason: altbootbank is invalid: /altbootbank is not a directory!

Any help to resolve those 2 issues? Thx

Capture.PNG

Reply
0 Kudos
paulsamkpz
Enthusiast
Enthusiast
Jump to solution

I increased my capacity to more than 20GB and the problem was solved.

Reply
0 Kudos
July22
Contributor
Contributor
Jump to solution

[SOLVED] Finally found and fixed my issue. Make sure that both bootbank and altbootbanks are good!

My upgrade problem wasn't due to lack of storage space, but bad bootbank partition on my ESXi boot usb. One of my bootbank partition were corrupted, so the upgrader couldn't unpack to the secondary bootbank partition!

This was a good guide that helped me --> Boot ESXi from a USB Flash Drive: A How-To-Guide

To fix it, I had to find & install the same version of ESXi to a new USB disk, and then restore my ESXi configuration.

Sound simple now! But took me a loooooooooooooooooooooooooooog while to figure out! Now, I'm on latest ESXi version 6.7 P01 !! Smiley Happy  Hope this helps someone else!

2) 2019-08-13T05:52:22Z esxupdate: HostImage: INFO: Installer <class 'vmware.esximage.Installer.BootBankInstaller.BootBankInstaller'> was not initiated - reason: altbootbank is invalid: /altbootbank is not a directory!

Reply
0 Kudos