ESXi host rebooted with the event "Assert + Voltage State Asserted" in SEL
Article ID: 431539
Updated On:
Products
Issue/Introduction
An ESXi host experiences an unexpected reboot.
The /var/log/vobd.log contains the following entry indicating a boot event:
YYYY-MM-DDTHH:MM:SS.SSSZ info hostd[######] [Originator@####sub=Vimsvc.ha-eventmgr] Event # : Host had been powered off. Last reboot reason is unknown. Please check ESXi and the BMC logs for further details. Please consult vSphere Documentation Center or follow the Ask VMware link for more information.
The /var/log/vobd.log contains the following entry indicating a boot event:
YYYY-MM-DDTHH:MM:SS.SSSZ: [GenericCorrelator] ########us: [vob.user.host.poweroff.reason.unavailable] Host had been powered off. Last reboot reason is unknown. Please check ESXi and the BMC logs for further details.
A review of the System Event Log (SEL) or hardware management logs shows a voltage assertion event coinciding with the reboot timestamp:
Event Type: 3 (Degraded/Warning)SEL Type: 2 (System Event)Message: Assert + Voltage State AssertedSensor Number: ##
To confirm this error is related to the processor, run the following localcli command. Match the decimal value in the first column (Node-Sensor) of the output with the Sensor Number from the error above:
# localcli hardware ipmi sdr listNode-Sensor Description Entity-Instance Computed Reading Base Unit Raw Reading Sensor Type
----------- --------------------------------- --------------- ----------------- ------------------- ----------- -----------
...#.## Processor # ##### ## # 3.1 State Deasserted assert-discrete 1 Voltage
Environment
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
Cause
The server hardware was restarted because of an CPU voltage issue.
Resolution
As this appears to be a hardware issue, coordinate with the hardware vendor to investigate further.
Additional Information
Feedback
