EC2/EBS Storage I/O Diagnostic Troubleshooter (Part 3)
Use the interactive troubleshooter below to identify your EC2/EBS storage I/O 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 |
|---|---|---|---|---|
| 1 | EBS — Underlying hardware failure, volume data unrecoverable | error: The underlying hardware related to your EBS volume has failed, and the data associated with the volume is unrecoverable. | A hardware failure occurred in the AWS infrastructure hosting the EBS volume, rendering the volume data unrecoverable. | N/A |
| 2 | volume — Volume stuck in "busy" state during detach | "VolumeId": "vol-1234abcd", "State": "busy" | The EBS volume is still mounted in the guest OS while the API detachment was requested, preventing a clean unmount. | sudo umount -d /dev/sdh |
| 3 | volume — Volume stuck in "detaching" state indefinitely | detaching: If your volume stays in the detaching state, you can force the detachment by choosing Force Detach. | The volume detachment process is delayed indefinitely due to OS locks or an unresponsive instance. | Choose Force Detach in the console, then perform file system check and repair procedures. |
| 4 | volume — ConcurrentSnapshotLimitExceeded on same volume | ConcurrentSnapshotLimitExceeded | The account reached the limit of pending snapshots for a single volume (1 for st1/sc1, or 5 for other volume types). | Wait for one or more of the pending snapshots to complete before creating another snapshot of that volume. |