- Newest
- Most votes
- Most comments
I made another instance and reinstalled all the software that I would like to use. I now run into the same problem on another new instance where I am unable to SSH into the instance again.
Instance ID: i-0ab43935f43fc87e9
***As of June 7 4:43 pm EST, I have terminated this second instance to save money but kept the first instance to see if there is any solution available from the community
Edited by: Kenny-Y on Jun 7, 2019 1:43 PM
Edited by: Kenny-Y on Jun 7, 2019 1:43 PM
Hello,
Looking over the first instance I can see from the console output the following;
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Press Enter for maintenance
(or press Control-D to continue):
With this error I can be due to a number of reasons: incorrect fstab, corrupt filesystem or a incorrect grub configuration.
Going forward you will need to stop the instance, detach the root volume and attach it as a secondary volume to an instance you can connect to. With this you will need to go to the secondary volume and diagnose the issue.
The following link shows other potential causes.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html#FilesystemGeneral-potential-cause
Relevant content
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 6 months ago