Confirmed that this article does work to fix the above error. Ran into the same issue upgrading single host from 5.0 to 5.5. Just change the path from /bootbank to /vmfs/volumes as displayed in the error code on the screen. You can safely reboot the host when the error comes up, as it will revert back to the previously installed version of vSphere.
I'm having the same issue.
Upgrading 5.0 to 5.1U1 from iso image .
Ran into the same error but there's no vua.log file in the /var/log/VMware folder
Changing dir to /bootbank brought me to a DIR where I can only find a state.tgz file
Any help is appreciated
I found it lately in /altbootbank
Messaggio modificato da Stefano
do you found the solution?
I exactly have the same issue with the same error number when I try to upgrade from 5.0 to 5.5.
As per KB, we need to check vua.log file which is not existing!
Any help is appreciated.
Here is the simple fix that you can do:
Move the local.tgz (in /altbootbank/state.xxxxx/) one directory higher.
ESXi has 2 memory banks that stores system image, they call it bootbank and altbootbank. When you upgrade, it will use altbootbank so that bootbank is preserved as a failsafe option. I moved local.tgz in /altbootbank/state.xxxxx/ one directory above and emptied the directory, upgrade worked on the next try.
Also, lets say for some reason upgrade (under /altbootbank) has some issue and gets messed up, then it will try the config in bootbank and comes up fine. local.tgz inside state.tgz holds the ESXi configuration. This can also be used to restore ESXi config when needed manually.
From below details, you can see that current it is running out of /bootbank/state.tgz
/vmfs/volumes/xxxxxxxxxxxxxxxxxxxxxxx # date
Wed Apr 9 11:58:04 UTC 2014
/vmfs/volumes/yyyyyyyyyyyyyyyyyyyyyyyy # pwd
/vmfs/volumes/yyyyyyyyyyyyyyyyyyyyyyyy # ls -la | grep state
-rwx------ 1 root root 21686 Apr 9 11:41 state.tgz
/vmfs/volumes/yyyyyyyyyyyyyyyyyyyyyyy # cd /altbootbank/
/vmfs/volumes/xxxxxxxxxxxxxxxxxxxxxxxxx # ls -la | grep state
-rwx------ 1 root root 17965 Apr 8 22:56 state.tgz
I am attempting an ESXi upgrade from 5.1 to 5.1 U2. However, after attempting to upgrade from a CD, I got the error specified at the top of the thread. I looked in /altbootbank and found two state.XXXXXX directories both containing local.tgz. I moved the local.tgz down a directory from the state.XXXXXX directory referenced in my error. However, after rebooting and re-running the installer, the installer doesn't find my installation and wants to overwrite the ESX partition. I rebooted again and moved local.tgz back to its original location and fired off the installer again but it still doesn't recognize my installation.
The ESXi host does still boot fine. Anyone have any thoughts on how I can upgrade this host? Any and all feedback is appreciated.
Did you manage to upgrade your host. I have exactly the same problem that after moving the local.tgz it doesn't find the installation and wants to do a fresh install. Please help.
At the end I redid a new installation
No, I haven't resolved this yet. I am planning to rebuild the affected hosts when time permits. If you or anyone else finds a resolution, please let me know.
I had the same problems: error 39 (folder not empty at 24%) or incompatibility vib update.
I need to update esxi 5.1 to 5.5 U1, when i try remove local.tgz next boot from cd the install don't show me upgrade host and preserve vmfs.
I try many many solutions but
The only one solution for me is:
1- esxcli command VMware-ESXi-5.1.0-Update1-1065491-HP-5.61.2-Sep2013-depot.zip
2-esxcli command update-from-esxi5.1-5.1_update02.zip
3-boot from cd with iso-VMware ESXi-5.5.0-1331820-HP-5.72.27-Feb2014.iso
and finally depot or update-from-esxi5.5-5.5_update01.zip or boot from cd with
I update 3 host in this way and now all run ...
I hope this can help.
1 person found this helpful
I ran into the same issue, the upgrade option was no longer available after emptying the stale.####### directories. I kept trying different things until I finally figured out a workaround. Copy the contents of bootbank to altbootbank and then try the upgrade again. The upgrade option should be available again. Hope this helps.
I'm glad I found this thread! I ran into this problem today upgrading a host from ESXi 5.5 Update 1 to 5.5 Update 2. I did a quick search and found that KB article from VMware that says how to move the local.tgz file (I found it in altbootbank) but then as others have reported here when I rebooted and attempted to upgrade again it only gave me the option to wipe out my data and install fresh. I always install ESXi to a flash drive so that didn't really bother me as I wouldn't lose my VMs but that particular host has several network connections on different VLAN's and I didn't want to try and rebuild it from memory so I held off on the ugprade thinking there must be a work around. I will try the suggestion about moving files from bootbank to altbootbank and will try to upgrade again next week and will report back.