1 Answer
- Newest
- Most votes
- Most comments
0
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.
Relevant content
- asked a year ago
- asked 2 months ago
- asked 3 years ago
- AWS OFFICIALUpdated 18 hours ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
I successfully mounted the volume, but I noticed that it contains the same files as the working instance. It seems like I've replicated the drive from the instance I'm using for testing. I've double-checked, and the volume I mounted is indeed from the non-working instance. I've also attached other volumes, but they exhibit the same behavior.
Is the device name "/dev/nvme2n1p2" correct?