1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
Contenuto pertinente
AWS UFFICIALEAggiornata un anno fa- AWS UFFICIALEAggiornata 2 anni fa
- In che modo posso risolvere i problemi di connessione alla mia istanza Linux Amazon EC2 tramite SSH?AWS UFFICIALEAggiornata un anno fa
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.