1 Answer
- Newest
- Most votes
- Most comments
1
Hello.
Judging from the error message, there seems to be a problem with the "/etc/fstab" settings.
Please mount the EBS root volume of the relevant EC2 instance on a normally running EC2 and check the settings in "/etc/fstab".
I think that the troubleshooting provided in the following documents will be helpful.
https://repost.aws/knowledge-center/ec2-linux-emergency-mode
This is just my guess, but there may have been some problem with the EC2 used to create the EC2 AMI used in the AutoScaling launch template.
If the EC2 that the AMI is based on still exists, you may be able to find out something by investigating that EC2.
Relevant content
asked a year ago
asked 3 months ago
- AWS OFFICIALUpdated 2 months ago
I have created the new AMI with a working EC2 instance. The new instance was working fine there was no mount error, and after a day all of sudden it also stopped responding. When I check the log and snapshot there are no errors. On the monitoring, the CPU was at 53 % usage.
I am still wondering how our existing instance which has been running for 6 months, all of sudden went down. No updates or setting changes have been made. Application has also no fault.
By the way, are there any differences between the "/etc/fstab" settings of the EC2 that is running normally and the EC2 that has experienced an error? What OS are you using on EC2? It's possible that this is a bug on the OS side, so it might be a good idea to check the forum sites for each OS.
Thank you for your comment.
Both EC2 instances have the same settings. Last year we replaced both EC2 instances with the same AMI images. Ubuntu 20.04.6 LTS is used as an OS. I will have a look into the Ubuntu forum as well.