EC2 Status Check Fails
I have launched an EC2 instance of g4dn.2xlarge type using this AMI
It was working very well but the last time I tried to start the instance and connect with it using SSH, I only the following error:
ssh: connect to host ___ port 22: Connection timed out
Then I found that the status check fails with the instance reachability check failed error as shown in the following figure.
I tried to look up a solution to this problem and I found those two posts: https://repost.aws/knowledge-center/ec2-linux-system-status-check-failure https://repost.aws/knowledge-center/ec2-linux-status-check-failure
And I tried to stop and start the instance and reboot it as mentioned in the previous links and waited for a day and tried again but with no luck.
After that, I tried to look into the system log of the instance and found the following issues:
- nvidia: module verification failed: signature and/or required key missing - tainting kernel
- Failed to start apply_instance_tag_service AWS Helper Service. See 'systemctl status apply_instance_tag_service.service' for details. Unmounting RPC Pipe File System..
Is there any other way to fix this problem and be able to connect to the instance?
- Mais recentes
- Mais votos
- Mais comentários
Based on the information you have shared, your instance might have booted in emergency mode. Reasons could be:
- A corrupted kernel.
- Auto-mount failures because of incorrect entries in the /etc/fstab.
You will need to launch the rescue instance and attach the current instance root volume into rescue instance to check and correct the /etc/fstab file. I would request you to follow the "Method 3: Manually edit the file using a rescue instance" mentioned in the following document to correct the entries in /etc/fstab.
https://aws.amazon.com/premiumsupport/knowledge-center/ec2-linux-emergency-mode/
Conteúdo relevante
AWS OFICIALAtualizada há 10 meses- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há um ano
Thanks for sharing this information. But the system log of the EC2 instance does not include any kernel panic or dependency failure errors. Are you sure this solution is suitable for my problem?