Difference between revisions of "Updating esxi"
Jump to navigation
Jump to search
Michael.mast (talk | contribs) |
Michael.mast (talk | contribs) |
||
(One intermediate revision by the same user not shown) | |||
Line 2: | Line 2: | ||
When trying to update from 6.0.0 to 6.7.0 I had two hosts that would not upgrade. They would also fail to patch as well. Following these instrauctions<ref>https://community.spiceworks.com/topic/2170328-vmware-dependecy-error-10302608?slot=slot_1</ref><ref>https://kb.vmware.com/s/article/56145</ref> I was able to get the upgrade to run. But first I had to obtain the profile name. I am sure this is stored in the XML file in the zip file, but I was able to pull it from the update manager in vcenter. | When trying to update from 6.0.0 to 6.7.0 I had two hosts that would not upgrade. They would also fail to patch as well. Following these instrauctions<ref>https://community.spiceworks.com/topic/2170328-vmware-dependecy-error-10302608?slot=slot_1</ref><ref>https://kb.vmware.com/s/article/56145</ref> I was able to get the upgrade to run. But first I had to obtain the profile name. I am sure this is stored in the XML file in the zip file, but I was able to pull it from the update manager in vcenter. | ||
+ | <pre>esxcli software profile update -p ESXi-6.7.0-20191204001-standard -d /vmfs/volumes/3263a783-96e197a0/ESXi670-201912001.zip</pre> | ||
+ | When using the Dell customized image I ran into a bunch of errors that vcenter was unable to overcome. The following is what I used, but I ended up reverting back to the image above. | ||
<pre> | <pre> | ||
esxcli software profile update -p DellEMC-ESXi-6.7U3-14320388-A02 -d /vmfs/volumes/3263a783-96e197a0/VMware-VMvisor-Installer-6.7.0.update03-14320388.x86_64-DellEMC_Customized-A02.zip | esxcli software profile update -p DellEMC-ESXi-6.7U3-14320388-A02 -d /vmfs/volumes/3263a783-96e197a0/VMware-VMvisor-Installer-6.7.0.update03-14320388.x86_64-DellEMC_Customized-A02.zip | ||
+ | </pre> | ||
+ | So in short you need to specify the profile and the update. Some of my hosts worked with this, but others just needed a clean install (After a 3 hour call with a VMware tech) | ||
+ | <pre> | ||
+ | esxcli software profile update -p ESXi-6.7.0-20191204001-standard -d /vmfs/volumes/3263a783-96e197a0/ESXi670-201912001.zip | ||
</pre> | </pre> |
Latest revision as of 18:34, 9 January 2020
Error Missing VIBs
When trying to update from 6.0.0 to 6.7.0 I had two hosts that would not upgrade. They would also fail to patch as well. Following these instrauctions[1][2] I was able to get the upgrade to run. But first I had to obtain the profile name. I am sure this is stored in the XML file in the zip file, but I was able to pull it from the update manager in vcenter.
esxcli software profile update -p ESXi-6.7.0-20191204001-standard -d /vmfs/volumes/3263a783-96e197a0/ESXi670-201912001.zip
When using the Dell customized image I ran into a bunch of errors that vcenter was unable to overcome. The following is what I used, but I ended up reverting back to the image above.
esxcli software profile update -p DellEMC-ESXi-6.7U3-14320388-A02 -d /vmfs/volumes/3263a783-96e197a0/VMware-VMvisor-Installer-6.7.0.update03-14320388.x86_64-DellEMC_Customized-A02.zip
So in short you need to specify the profile and the update. Some of my hosts worked with this, but others just needed a clean install (After a 3 hour call with a VMware tech)
esxcli software profile update -p ESXi-6.7.0-20191204001-standard -d /vmfs/volumes/3263a783-96e197a0/ESXi670-201912001.zip