Initially I had created my default linux instance. Then later I created new volume of 2 GB and attached to my linux instance. Within the linux instance I did some modifications such as creating a folder name volume1 and attached the 2 GB volume to it. To avoid mounting everytime after a server reboot, I went to mtab and copied information regarding the 2 GB storage mounting and pasted the same in fstab to just use mount -all option to automatically attach all the volumes available. Later I detached and deleted the 2 GB volume from my linux EC2 instance. When I launch my EC2 instance it fails the status checks and the instance doesnot load up. I have confirmed that the volume is in the same availability zone as the instance, and the relevant security group has the correct inbound rules. I guess there is some issue happening relating the statement of the detached 2 GB volume present in fstab file of my main linux EC2 instance. Can you help me in regard of this ? I am not able to launch my EC2 instance.
I checked for system log for my main linux instance, I got the following in the end lines:
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.
AWS 공식업데이트됨 일 년 전
If you think you have an invalid fstab entry, have you tried removing it? Here is some info about how to do so from a separate EC2 instance -> https://aws.amazon.com/premiumsupport/knowledge-center/ec2-linux-emergency-mode/