1 Answer
- Newest
- Most votes
- Most comments
1
- Stop the broken instance
- Detach the root volume from the broken instance
- Boot up a new instance that you can log in to
- Attach volume from broken instance to the new instance
- Mount the volume at the OS level
- Reinstall the missing library
- Detach volume from new instance
- Attach fixed volume back the broken instance
- Boot up instance.
Relevant content
- asked 2 months ago
- asked 5 years ago
- asked a year ago
AWS OFFICIALUpdated 8 months ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
it work! thank you so much, it save my job.
let's tell more about details to help guys with the same problem.
When meet "wrong type" while mount volumns, we can use the following command line. mount -t xfs -o nouuid /dev/nvme2n1p2
the aws attach page tell you it will mount at /dev/sda, actually you can't find it in ec2. the attach volumns real dev name in instance is show bying the cml: lsblk -f. The dev without mount path is the new volumn we found.