Despite your best efforts, Cloud Servers occasionally encounter an internal issue that causes them to lose their connection so you can’t reach the Cloud Server. In these cases, SpinUp recommends that you attempt to troubleshoot the Cloud Server by using rescue mode.
You should have the following:
A valid SpinUp account
A Cloud Server to be rescued
What is rescue mode?
Rescue mode enables you to access unresponsive devices by building an alternate operating system and attaching your normal device’s disk.
This is very similar to using a USB or CD-ROM boot device to start a local
machine. The hypervisor downloads an OS image, boots it, and then attaches your
regular device’s disk as a secondary disk to the rescue environment. This allows
you to troubleshoot issues, to perform disk actions, such as using the
diagnostic command, and to recover data in case the device can’t be fixed.
If this happens, see What is a host server down? for more information.
Situations for rescue mode
You should use rescue mode only if you cannot access the Cloud Server in any other way.
SpinUp recommends attempting to reach the Cloud Server by using Secure Shell (SSH), Remote Desktop Protocol (RDP), or the web console before using rescue mode. If you can get access to the Cloud Server with one of these methods, you can quickly start troubleshooting rather than waiting for rescue mode to apply.
If you can’t reach the Cloud Server by using any other methods, then you should use rescue mode to access the device. Rescue mode has a time limit of 24 hours as it does require some additional resources on the host machine. However, if you are unable to resolve the issue within 24 hours, you can simply re-rescue the Cloud Server to continue troubleshooting.
Place a Cloud Server in rescue mode
First, navigate to the Cloud Server Details page in the Control Panel for the device in question. Click on Cloud Servers in the left navigation menu and then click the appropriate Cloud Server.
On the Details page, click the RESCUE and in the dialog that comes up, confirm your decision.
- Make sure to make note of the provided rescue password because this is the only time the password is displayed.
- After you confirm, the system starts building out the rescue environment. This process normally takes just a few minutes. After the Cloud Server status updates from rescuing to rescued, the Cloud Server is ready.
Troubleshooting a Cloud Server in rescue mode
After you put the Cloud Server in rescue mode, you should be able to access it by using SSH or RDP as usual.
Be sure to use the provided rescue password instead of your normal credentials. After you are logged in to the rescue environment, your regular Cloud Server disk is available but unmounted.
If you believe the device encountered a disk issue, SpinUp recommends performing a filesystem check on your volume.
For Linux® systems, leave the disk unmounted and run
For Microsoft® Windows® systems, the rescued disk is attached to the
Cloud Server but offline and unmounted. You must bring the disk online to determine
whether there is file system corruption. After the disk is online, use
to identify and correct corruption.
These are both automated utilities that try to identify and correct any errors with the filesystem.
If the issue is not related to the disk, or the disk diagnostic utility comes back clean, then we recommend that you mount the disk to investigate possible causes by reviewing the device’s logs and configuration files. Changes made to the original disk while in rescue do apply even after the rescue, allowing you to fix the issue and then unrescue the Cloud Server.
Remove a Cloud Server from rescue mode
Removing a Cloud Server from rescue mode is just as straightforward as placing a Cloud Server into rescue.
First navigate to the Cloud Server Details page again, if you do not still have it open.
Once again, the system takes a few minutes to remove the Cloud Server from rescue mode. After the status updates to Active, you can access and use the Cloud Server as usual.
After coming out of rescue, any changes made to the Cloud Server’s disk inside rescue mode are present, and if those changes resolved the issue, your Cloud Server should now boot normally.