EBS Volume Booting issue with New Volume

0

After detached the volume only we can delete it to avoid the charges, but after creating the new volume we can attached the new volume into the instances its successfully attached but when we try to connect it again we the new volume its not booting the test 2/2 is not passing through why?

asked 5 months ago72 views
1 Answer
0

Hi there!

From the notes, I understand that your EC2 instance is failing the status check after attempting to detach and attach a new volume.

For guidance, reasons that can cause an instance to fail to boot are:

  1. Using incorrect device names when attaching the volume [1].
  2. Incorrect entries in the fstab file due to booting from secondary volumes attached to the instance. Please refer to document link [2] to troubleshoot issues when booting from a different volume.

To troubleshoot the issue from your side, you can check the instance's system logs to determine the cause of the failure [3]. Depending on the cause of failure you may use [4] to further troubleshoot.

I hope you find the above information helpful.

Have a great day ahead!

References:

[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/RootDeviceStorage.html [2] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-booting-from-wrong-volume.html [3] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html#troubleshooting-retrieve-system-logs [4] https://aws.amazon.com/premiumsupport/knowledge-center/ec2-linux-status-check-failure/

Letty
answered 5 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions