Re-attaching EB volume makes instance fail status checks

0

I detached and deleted a EB volume from an EC2 instance. After creating a new volume (basically identical to the previous volume) and attaching it to the EC2 instance, when I launch the instance it fails the status checks and the instance stops. I have confirmed that the volume is in the same availability zone as the instance, and the relevant security group has the correct inbound and outbound rules.

asked 3 years ago404 views
6 Answers
0

Hi tjbrailey

Thank you for reaching out to us :)

Could you please provide an error message. You can get this by retrieving system logs which will allow me to troubleshoot this issue accordingly.

Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/  
  1. In the navigation pane, choose Instances, and select your instance.

  2. Choose Instance state, Reboot instance. It might take a few minutes for your instance to reboot.

  3. Verify that the problem still exists; in some cases, rebooting may resolve the problem.

  4. When the instance is in the running state, choose Actions, Monitor and troubleshoot, Get system log.

  5. Review the log that appears on the screen, and copy the system log error statements and paste into a reply in order for me to troubleshoot your issue.

I look forward to your response :)

naz97
answered 3 years ago
0

Many thanks for your response.

I completed points 1. - 3. and the problem still exists.

For 4. - 5., when I open up the system log, I see a black panel. If I try to copy or download the log, there is no text.

answered 3 years ago
0

Thank you for confirming steps 1 -3 :)

Could you please provide some more information on how you created the new volume? Such as whether you have created an EBS volume from scratch, meaning, you have gone through the configurations by selecting the volume type, size, etc or if you have created an EBS volume from a snapshot.

When you create an EBS volume based on a snapshot, the new volume begins as an exact replica of the original volume that was used to create the snapshot. The replicated volume loads data in the background so that you can begin using it immediately. On the other hand, if you have created your EBS volume from scratch it would be an empty volume with no data.

Just for note, it is best practices to back up your data on EBS volumes by taking snapshots before deleting them:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSSnapshots.html

I look forward to your response.

naz97
answered 3 years ago
0

Got it, thanks for the information.

I set up a new volume from scratch, so I think this is causing the problem. I don't have any snapshots, so is there a way to attach a new volume and access the instance, or would I need to create a new instance from scratch?

Thanks

answered 3 years ago
0

Thank you for the confirmation :)

Based on your reply, that the volume was created from scratch and would therefore be empty, there is no way to install an Operating System onto it. It would be advisable to terminate and create a new Linux instance which will contain the root device volume that will have the image used to boot the instance

Feel free to reach out if you require any assistance :)

naz97
answered 3 years ago
0

Okay great, many thanks for your help on this.

answered 3 years 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