Check the output to verify that there are vmlinuz and initramfs files corresponding to the kernel version that you want to boot. Run the following commands: cd /rescue/bootĢ. The vmlinuz and initramfs files are necessary to boot successfully.ġ. If a Kernel Panic error message is in the system log, then the kernel might not have the vmlinuz or initramfs files. For additional errors, see Troubleshooting system log errors for Linux-based instances. The following is a list of common errors that cause instance status check failure. The next steps depend on the error message listed in the system log. If you haven't already done so, retrieve the system log of the instance to verify the error. To determine the correct device name, run the lsblk command to view your available disk devices along with their mount points.Ĩ. Note: The device (/ dev/xvdf1) might be attached to the rescue instance with a different device name. If you receive an error, such as Wrong Fs type or UUID duplicate, Superblock is missing or badblock found, see Why can't I mount my Amazon EBS volume? Create a mount point directory (/ rescue) for the new volume attached to the rescue instance: $ sudo mkdir /rescueħ. Connect to your rescue instance using SSH.Ħ. Attach the volume as a secondary device ( /dev/sdf) to the rescue instance.ĥ. Note the device name ( /dev/xvda or /dev/sda1) of your root volume.Ĥ. Detach the Amazon Elastic Block Store (Amazon EBS) root volume ( /dev/xvda or /dev/sda1) from your impaired instance. The existing instance must use the same AMI and be in the same Availability Zone as your impaired instance.ģ. The new instance becomes your rescue instance. Use the same Amazon Machine Image (AMI) and the same Availability Zone as the impaired instance. Launch a new EC2 instance in your virtual private cloud (VPC). For more information, see How do I use EC2Rescue for Linux to troubleshoot operating system-level issues? Manually correct errors using a rescue instanceġ. Run the EC2Rescue for Linux toolĮC2Rescue for Linux automatically diagnoses and troubleshoots operating systems on unreachable instances. Note: If you receive errors when running AWS CLI commands, make sure that you're using the most recent version of the AWS CLI. For information on configuring the EC2 serial console for Linux instances, see Configure access to the EC2 serial console. If your instance is unreachable and you haven't configured access to the serial console, then follow the instructions in Run the EC2Rescue for Linux tool or Use a rescue instance. If you're using the EC2 serial console for the first time, then make sure that you review the prerequisites, and configure access before trying to connect. To access the serial console, use the Amazon EC2 console or the AWS Command Line Interface (AWS CLI). The serial console connects to your instance without needing a working network connection. The serial console helps you troubleshoot boot issues and network and SSH configuration issues. If you turned on the EC2 serial console for Linux instances, then you can use it to troubleshoot supported Nitro-based instance types and bare metal instances. Use the EC2 serial console for Linux instances To retain a public IPv4 address that doesn't change when the instance is stopped, use an Elastic IP address.įor more information, see What happens when you stop an instance. The static public IPv4 address that Amazon EC2 automatically assigned to the instance on launch or start changes after the stop and start. Unlike Amazon Elastic Block Store (Amazon EBS)-backed volumes, instance store volumes are ephemeral and don't support data persistence. Make sure that you save a backup of the data before stopping the instance. Data that's stored in instance store volumes is lost when the instance is stopped. Important: Some of the following procedures require stopping the instance. There are three methods for troubleshooting OS issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |