Hi, thank you for your question. In most cases, starting and stopping your instance will migrate the instance to another physical host computer . 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 .
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 .
Do all EBS volumes have only 2 IO queues?asked 7 months ago
Multiple EBS volumes to gain perfomanceAccepted Answerasked a year ago
getting 502 bad gateway errors every time I turn on ec2 instanceasked 4 months ago
I need export Once EC2 Instance but show error message "This instance has multiple volumes attached"asked 8 months ago
How are EBS volumes in an unhealthy instance handled when a new instance is created by Auto Scaling?Accepted Answerasked 2 years ago
Attachment order for EBS volumes as /dev/nvme devicesasked 3 months ago
Understand RDS PIOPS, EBS IO and EBS BYTE Balance (%) ?asked 3 months ago
EC2 Instance with recurrent I/O errors, but fsck reports filesystems as cleanasked 7 months ago
How is Provisioned IO charged?Accepted Answerasked 2 years ago
CloudWatch disk_used_percent alerts for multiple volumes on Nitro instanceAccepted Answerasked 3 years ago