Rackspace Cloud Essentials - Rescue Mode on Linux Cloud Servers
If your Linux system has become non-bootable or is suffering from critical system errors, you can use rescue mode to recover your system data. These problems may be caused by file system corruption, boot file corruption, or other configuration errors. Normally, if your system encounters any problem during the boot process, you would boot in to a maintenance mode environment known as Single User Mode that would allow you to login with your root password and check for any errors. Using Single User Mode can cause the following issues:
Your system is read-only and you cannot make corrective changes. Most services such as networking are disabled. This would prevent you from copying your data to another server.
You would have to access your server using the Console, which is slower than using a traditional SSH login.
To avoid having to use single user mode, start your server up in rescue mode in the Cloud Control Panel.
Put your server into rescue mode
Rescue mode grants the root user full access to your non-bootable server’s filesystem. You can use it to modify problems in configuration files or to copy data from your Cloud Server to a remote location. Rescue Mode through the Cloud Control Panel is similar to booting into single-user mode with networking enabled.
Log in to the Cloud Control Panel and select Servers.
Click the gear menu next to the server and select Enter Rescue Mode.
Read the information in the pop-up window, then press Enter Rescue Mode.
Copy the temporary password and click Dismiss Password.
Note: The green bar to the left of the server name will turn yellow during the process of building into Rescue Mode and then red when the process has completed. This may take several minutes.
After your server is in rescue mode, use an SSH client to connect to your server using the public IP address and the temporary root password to log in to rescue mode.
Troubleshoot your server in rescue mode
Before you can access the files on your server, you must mount the server’s file system. To do that, look at your partitions to determine your file system’s device.
Note: If you plan to use
fsck on this filesystem, DO NOT MOUNT the filesystem.
Log into your server in rescue mode and run the following command:
You will get the following output:
Note the different disk names. The disk entry will display the device and size of the disk. For example: Disk /dev/xvdb1: 20 GiB
The first block, /dev/xvdb1, with size 20 GiB, is the rescue mode filesystem.
The second block, /dev/xvda1, with size of 20 GiB, is the server’s file system. The size will vary depending on the size of your server.
If a third block is displayed, it is the swap volume. Note: This only occurs only on older cloud servers).
When you’ve identified the block for your server’s file system, note the part after
diskthat looks like a file path. In the example above, the device is /dev/xvda1. The device will vary depending on the distribution image used to build your server. Now that you know your file system’s device, you can assign it a directory and mount it for access. Plug your file system device into the following command in place of /dev/diskdevice.
mount /dev/diskdevice /mnt
For example, for /dev/sda1 the command would be:
mount /dev/xvda1 /mnt
Now you can access your files through the /mnt directory. Just remember that you’ll need to put “/mnt” in front of the usual paths you’d use to get to files. For example, if you have a problem in the /etc/fstab file you need to fix, you’d actually access that file at:
If you just edit /etc/fstab while in rescue mode, you will change the
fstabfor the rescue mode file system, not your normal file system.
Exit rescue mode
Once you are done troubleshooting your system, click Exit Rescue Mode in the Cloud Control Panel on your Server Details page.
Continue the conversation in the Rackspace Community.
©2016 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License