EC2 Instance type results in reachability failure

0

I have a r5.24xlarge instance with Windows 2016 + SQL Server 2017. All working good. Shut it down, changed instance type to x2iedn.8xlarge, started instance and now cannot reach instance. Instance status check shows "Instance reachability check failed". System status check passed. Instance screenshot shows Windows logon screen...

What could be wrong? How do I troubleshoot this?

已提问 1 年前267 查看次数
2 回答
0

Hi There

Please take a look at this troubleshooting article that talks about issues when upgrading drivers or changing instance types.

Here is documentation about the compatibility of different instance types and AMI's.

Since the instance screenshot shows the Windows logon screen, it sounds like the network card is not coming up. You can try switching back to the R5 instance type and follow steps 1, 2, and 3 from this guide to update all of the required drivers, and then try switching instance types again.

profile pictureAWS
专家
Matt-B
已回答 1 年前
0

Failure to check the status of an instance indicates that the instance may have the following problems

Network or startup configuration problems Exhausted memory File system problems Operating system startup failure Volumes not mounted properly Incompatible drivers Exhausted CPU https://aws.amazon.com/jp/premiumsupport/knowledge-center/ec2-windows-instance-status-check-fail/

Troubleshooting for EC2 Windows instances can be found below.

https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/troubleshooting-windows-instances.html

已回答 1 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则