Instance reachability check failed

Question

Despite multiple attempts to resolve the issue, I am still unable to access our Linux EC2 instance. I have restarted the instance several times including stopping/starting and checked the system logs, which is blank. Additionally, my efforts to access the instance using the serial console connection have been unsuccessful because it's also a black screen. I've also tried restoring the instance using backup AMIs and different snapshots, but I encounter the same issue each time. Unable to use Ec2Rescue as I am unable to mount the root volume. Error says "mount: /mnt/xfs_mount: wrong fs type, bad option, bad superblock on /dev/nvme2n1p2, missing codepage or helper program, or other error." I am mounting as XFS

sudo mount /dev/nvme2n1p2 /mnt/xfs_mount Also tried mount -t xfs /dev/nvme2n1p2 /mnt/xfs_mount

Unsure how to troubleshoot without anything appearing in the system log and no serial console access.

sudo mount /dev/nvme2n1p2 /mnt/xfs_mount
Also tried mount -t xfs  /dev/nvme2n1p2 /mnt/xfs_mount

Unsure how to troubleshoot without anything appearing in the system log and no serial console access.

Answer

Hello.

I think that the EBS volume UUID is probably duplicated and the mounting is failing.  
EBS snapshots create identical copies block by block, so if you use EC2 using the same AMI, the UUIDs may match.  
https://docs.aws.amazon.com/ebs/latest/userguide/ebs-snapshots.html#how_snapshots_work

So, when mounting, try running the command with the "-o nouuid" option as shown below.  
https://repost.aws/knowledge-center/ebs-mount-volume-issues  
```
mount -t xfs -o nouuid /dev/nvme2n1p2 /mnt/xfs_mount
```

If the mounting is successful, you can check the system logs etc. inside the EBS volume, so you can continue troubleshooting.

Instance reachability check failed

관련 콘텐츠