EC2 Hypervisor / Hardware / Scheduled Event Diagnostic Troubleshooter (Part 2)
Use the interactive troubleshooter below to identify your EC2 hypervisor, hardware, or scheduled event symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 5 | scheduled event / system-reboot — Network or power maintenance on underlying host | curl http://169.254.169.254/latest/meta-data/events/maintenance/scheduled / "Code" : "system-reboot" / "State" : "active" | AWS must perform network or power maintenance on the underlying host, resulting in a scheduled event. | Stop and start the instance to migrate it to a new host, or automate the action with Amazon EventBridge. |
| 6 | numa — ENA driver NUMA node override module parameters | parm: numa_node_override_array:Numa node override map / parm: numa_node_override:Enable/Disable numa node override (0=disable) | Module parameters exposed when checking the ena (Elastic Network Adapter) driver via modinfo ena using DKMS on Ubuntu. | N/A |
| 7 | hardware error — StatusCheckFailed_System due to physical host failure | System status checks monitor the AWS systems on which your instance runs... Hardware issues on the physical host that impact network reachability | The underlying physical host hardware failed, causing a loss of network connectivity or power and triggering a StatusCheckFailed_System error. | Stop and start the EBS-backed instance to migrate it to a new, healthy underlying host. |