EC2/EBS I/O Error / Storage Diagnostic Troubleshooter (Part 1)
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 |
|---|---|---|---|---|
| 1 | I/O error — end_request: I/O error, dev sde | [9943662.053217] end_request: I/O error, dev sde, sector 52428288 | A physical drive or an Amazon EBS volume has failed. | N/A (Terminate the instance and launch a new instance; recover data from backups or recent snapshots). |
| 2 | I/O error — Buffer I/O error on device md0 | Buffer I/O error on device md0, logical block 209713024 | The underlying block device (Amazon EBS volume or physical drive) experienced a hardware or storage-level failure. | N/A (Terminate the instance and launch a new instance). |
| 3 | I/O error — drbd: neither local nor remote disk | block drbd1: IO ERROR: neither local nor remote disk / JBD2: I/O error detected when updating journal superblock for drbd1-8. | A failed Amazon EBS volume or failed physical drive has caused a broken distributed block device state. | N/A (Terminate the instance and launch a new instance; recover from a recent snapshot if EBS-backed). |
| 4 | corrupt — superblock corrupt | fsck.ext3: No such file or directory while trying to open /dev/sdh / The superblock could not be read or does not describe a correct ext2 filesystem... | A bug exists in ramdisk filesystem definitions, misconfigured /etc/fstab, or the drive is missing/failed. | e2fsck -b 8193 <device> |