esstokes1
Enthusiast
Enthusiast

Install-VMHostPatch causes host to purple screen

I'm trying to update hosts from ESXi 5.0 U2 to 5.0 U3 using update-from-esxi5.0-5.0_update03.zip.  I'm using PowerCLI 5.1 R2.  Here are my steps after connecting to my VC:

$vmhost = Get-VMHost -Name myhost.domain.net

$metazip = "/vmfs/volumes/SAN-DATASTORE01/ESXi-5.0.0-20131002001/metadata.zip  # tried changing ESXi-5.0.0-20131002001 to ESXi-5.0.0-20131002001-standard to match the profile in update-from-esxi5.0-5.0_update03.zip

Install-VMHostPatch -VMHost $vmhost -HostPath $metazip

Here's the output:

WARNING: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

IsApplicable IsInstalled NeedsReconnect NeedsRestart

------------ ----------- -------------- ------------

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        True        False          False

False        False       False          False

False        False       False          False

False        True        False          False

False        False       False          False

False        True        False          False

False        True        False          False

False        True        False          False

False        True        False          False

False        True        False          False

It appears to install correctly but when I reboot the server it purple screens and then on reboot it loads 5.0 U2.  I was just wondering if anyone else had seen this or if there is something wrong with how I'm using Install-VMHostPatch.  I also tried this using the InstallHostPatchV2_Task method with the HostPatchManager object and I'm seeing purple screen there as well.  Is it ok to have the patch on a shared datastore or does it need to be on a local datastore?

Thanks

Eric

0 Kudos
4 Replies
LucD
Leadership
Leadership

What is the purple screen indicating ?

See KB1004250


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
esstokes1
Enthusiast
Enthusiast

Here's the purple screen.  I can open an SR about the purple screen but I think this has to do with Install-VMHostPatch (or the options I'm entering) since I've patched a number of ESXi servers using this same zip file with the 'esxcli software profile update' comand namespace successfully.

purplescreen.png

0 Kudos
LucD
Leadership
Leadership

That's a page fault, you would require a core dump and VMware support to determine what is happening.

If you do this upgrade with the Update Manager, do you get the same purple screen ?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
esstokes1
Enthusiast
Enthusiast

No Update Manager in our environment but even using PowerCLI with Get-ESXCli works to install the update.  I created an array that has the path to all the vibs in the zip file and tried to install using the Install_HostPatchV2 method.

$patchManager = get-view -id $vmhost.ExtensionData.configManager.patchManager

$results = $patchManager.InstallHostPatchV2($null,$null,$vibs,$null)

According to vCenter, the Install task completed successfully but when I look at $results I get this:

Version         : 1.40

Status          :

XmlResult       : <esxupdate-response>

                  <version>1.40</version>

                  <error errorClass="ValueError">

                    <errorCode>99</errorCode>

                    <errorDesc>VIB VMware_bootbank_scsi-hpsa_5.0.0-17vmw.500.3.41.1311175 obsoletes VIBs VMware_bootbank_scsi-hpsa_5.0.0-17vmw.500.0.0.469512 in the input to AddVibs -- cannot continue</errorDesc>

                  </error>

                  </esxupdate-response>

I'm thinking scsi-hpsa isn't being updated and that's causing the problem.  Looking at the purple screen image it says that "No place on disks to dump data" but I checked after rebooting back into 5.0 U2 and the esxcli system coredump partition list command shows a partition is active and configured.  I'm not sure there is much else that can be done here - I was hoping someone would be able to try the same and see if this works for them but it might be specific to HP hardware.

0 Kudos