EBS Automated Backup DR Gap / Durability Risk Diagnostic Troubleshooter (Part 2)
Use the interactive troubleshooter below to identify your EBS automated backup DR gap or durability risk 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 | Permanent Snapshot Restore Failure (Recovery Blocked) | "event": "permanentRestoreSnapshot" "result": "failed" "cause": "Source snapshot ID is not valid" | The permanent restore action from the EBS Snapshots Archive tier failed due to an invalid source snapshot ID, completely blocking volume recovery. | N/A |
| 6 | EBS Volume Data Inconsistency (I/O Disabled) | Awaiting Action: Enable IO Volume data is potentially inconsistent. I/O is disabled for the volume until you explicitly enable it. | Amazon EBS detected potential data inconsistency on the volume and automatically disabled I/O to prevent further data corruption. | aws ec2 enable-volume-io |
| 7 | Instance Failover/Reboot Failure (Unbootable System) | Errors in the /etc/fstab file can render a system unbootable. Do not shut down a system that has errors in the /etc/fstab file. | The /etc/fstab file contains errors or lacks the nofail mount option for an attached EBS volume, which permanently halts the boot process. | [ec2-user ~]$ sudo mv /etc/fstab.orig /etc/fstab |
| 8 | Hardware Failure / Impending Data Loss (Instance Store) | "Code": "instance-stop" "Description": "The instance is running on degraded hardware" | AWS detected an irreparable failure of the underlying physical hardware and scheduled the instance for retirement, meaning any data on ephemeral instance store volumes will be permanently lost upon termination. | N/A |