- 最新
- 最多得票
- 最多評論
T3 is a Nitro-based instance type, T2 is not https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html#nitro-instance-types
I think it would be advisable to read the knowledge document Why is my Linux instance not booting after I changed its type to a Nitro-based instance type? and follow the recommended steps.
This also a good third-party explainer https://www.continuent.com/resources/blog/how-convert-aws-instance-family-t2-t3-enhanced-networking-amazon-linux-1
Also, when the instance is up and 2/2 checks passed and you're not able to SSH into it, are you able to connect using AWS Systems Manager Session Manager? https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-prerequisites.html
Hi, Please check the below steps and share the status if it doesn't work properly.
- Please check the inbound ssh port, 22, is opened properly.
- Check the DNS is solved at the client.
$ dig <EC2 endpoint>
- EC2 is deployed in a public subnet.
Hi,
Some other folks had similar issues in the past and fixed them: https://repost.aws/questions/QUG_Q2Tu0cQemkhTMoISVLtQ/convert-a-t2-instance-to-t3
Best,
Didier
Thanks for all the assistance! It appears the issue was related to an EBS volume. I had created and attached an EBS volume to the instance when it was a t2 instance, where the volume was mounted as /dev/xvdf. However, when changing the instance type to t3, the device name for the EBS volume changed, causing the fstab to fail and the instance to enter emergency mode.
相關內容
- 已提問 6 個月前
AWS 官方已更新 2 年前- AWS 官方已更新 2 年前
Hello Hyp,
Thank you for your assistance and response.
I have checked all the suggestions you provided, and everything appears to be working correctly. Moreover, I also considered that there might be an issue with the SSH client on the machine. To test this, I attempted to connect via the 'Serial Console' and 'Instance Connect' methods, but both attempts failed.