- Newest
- Most votes
- Most comments
Hi, thank you for your question. In most cases, starting and stopping your instance will migrate the instance to another physical host computer [1]. If you have stopped/started the instance multiple times and the I/O errors persist, it is likely that the problem lies within the instance itself, rather than the underlying host/hardware. Please refer to this guide for help troubleshooting common I/O errors within your EC2 instance [2].
Additionally, 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 [3].
[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html
[2] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html
[3] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-io-characteristics.html
Relevant content
- asked 2 years ago
- asked 9 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 10 months ago