Skip to main content

EC2/EBS Storage I/O Diagnostic Troubleshooter (Part 1)

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

#ScenarioKey Error SignalRoot CauseThe Fix
1read-only — Filesystem remounted as read-only due to NVMe I/O timeout"If I/O latency exceeds the value of this timeout parameter, the Linux NVMe driver fails the I/O and returns an error to the filesystem or application... In some cases, your filesystem might be remounted as read-only."I/O latency exceeded the OS NVMe driver's default 30-second timeout threshold.Set boot parameter nvme_core.io_timeout=4294967295.
2EBS / impaired — Volume data potentially inconsistent, I/O disabled"After I/O is disabled, the next volume status check fails, and the volume status is impaired... Awaiting Action: Enable IO... Volume data is potentially inconsistent."Amazon EBS detected potentially inconsistent data and proactively disabled I/O to prevent data corruption.Run aws ec2 enable-volume-io or enable the Auto-Enabled IO (autoEnableIO) attribute.
3degraded — I/O performance status check: Degraded"I/O performance status check... Degraded... For io1, io2, and gp3 volumes only. Volume performance is below expectations."Actual volume performance dropped below expected levels, which frequently happens while initializing volumes restored from snapshots.N/A (Usually resolves once volume initialization from snapshot completes).
4stalled — I/O performance status check: Stalled"I/O performance status check... Stalled... For io1, io2, and gp3 volumes only. Volume performance is severely impacted."Volume performance was severely impacted, indicating the volume is struggling to process I/O due to infrastructure constraints or exhausted throughput limits.N/A