EC2/EBS I/O Error / Storage Diagnostic Troubleshooter (Part 2)
Use the interactive troubleshooter below to identify your EC2/EBS I/O error or storage 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 | corrupt — File system is corrupt, fsck required | If you get an error stating that the file system is corrupt, run the following command to use the fsck utility to check the file system and repair any issues: | The attached EBS volume's file system has become corrupted and requires repair. | sudo fsck /dev/xvdf1 |
| 6 | volume — I/O paused by AWS FIS, volume status impaired | If you drive I/O to a volume that has I/O paused, the following happens: The volume's status transitions to impaired within 120 seconds. / The CloudWatch metrics for queue length (VolumeQueueLength) will be non-zero. | I/O operations between the Amazon EBS volume and the instance have been temporarily paused by AWS Fault Injection Simulator (FIS). | N/A |
| 7 | degraded — I/O performance degraded temporarily | Also, a volume's I/O performance may become degraded temporarily due to an action you have taken (for example, creating a snapshot of a volume during peak usage, running the volume on a non-EBS-optimized instance, or accessing data on the volume for the first time). | I/O performance is throttled due to uninitialized blocks on a restored snapshot, non-EBS-optimized instance limits, or snapshot overhead. | sudo dd if=/dev/xvdf of=/dev/null bs=1M |
| 8 | volume — Provisioned IOPS SSD volume warning state during initialization | While initializing Provisioned IOPS SSD volumes that were created from snapshots, the performance of the volume may drop below 50 percent of its expected level, which causes the volume to display a warning state in the I/O Performance status check. | The volume is currently downloading storage blocks from Amazon S3, causing a significant increase in I/O latency. | N/A (This is expected behavior and can be ignored while the volume initializes). |