Help improve AWS Support Official channel in re:Post and share your experience - complete a quick three-question survey to earn a re:Post badge!
IO Errors in EC2 instance
Recently, we found that our EC2 instance was not responding. We tried to login to the VM but timed out. When we tried to "reboot" the instance from AWS Console, the console showed some IO Errors as shown in the attached screendump.
Finally, I stopped and started the instance again before it is working again.
Is this a problem with the EBS?
- Newest
- Most votes
- Most comments
Hello
Please try this solution.
To address IO errors on your EC2 instance start by stopping and starting the instance from the EC2 Console to potentially resolve transient issues. check the state and status of the attached EBS volume in the Volumes section if issues are detected, create a snapshot of the volume, then use this snapshot to create a new volume. Detach the problematic volume and attach the new one to the instance. If filesystem corruption is suspected, SSH into the instance (or use RDP for Windows) and run a filesystem check (Ex. fsck for Linux or chkdsk for Windows). Set up monitoring and alarms in CloudWatch for CPU, disk IO, and instance status checks to proactively manage resources. please ensure that your read/write IOPS are not exceeding the capacity of your EBS volumes. You can view your read/write IOPS by monitoring the VolumeReadOps and VolumeWriteOps volume metrics in CloudWatch.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html https://docs.aws.amazon.com/ebs/latest/userguide/ebs-io-characteristics.html https://manpages.ubuntu.com/manpages/xenial/en/man8/mount.8.html https://docs.aws.amazon.com/ebs/latest/userguide/ebs-using-volumes.html
