Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.xloud.tech/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Rescue mode boots an instance from a temporary rescue image while preserving the original root disk as a secondary device. This allows you to diagnose and repair boot failures, corrupted filesystems, or locked-out SSH configurations without destroying the instance.
Prerequisites
  • An instance in Active or Shutoff status
  • The instance must not be locked
  • CLI access required — the Rescue action is not available in the Dashboard GUI
The Rescue and Unrescue actions are CLI-only operations. They are not available in the Xloud Dashboard. Use the CLI commands below to enter and exit rescue mode.

​
Enter Rescue Mode

1

Authenticate

Load credentials
source openrc.sh
2

Rescue the instance

Enter rescue mode (default rescue image)
openstack server rescue <INSTANCE_ID>
Rescue with a specific image
openstack server rescue \
  --image <RESCUE_IMAGE_ID> \
  <INSTANCE_ID>
The instance reboots into rescue mode. The original root disk is attached as a secondary device (typically /dev/vdb).
3

Connect and repair

SSH into the instance using the rescue image credentials. Mount the original root disk and perform repairs:
Mount the original root disk
sudo mount /dev/vdb1 /mnt
Example: fix SSH config
sudo vi /mnt/etc/ssh/sshd_config

​
Exit Rescue Mode

Unrescue the instance
openstack server unrescue <INSTANCE_ID>
The instance reboots from its original root disk with the repairs applied.
Instance returns to Active status on its original root disk.

​
Next Steps

Instance Snapshots

Create a snapshot before rescue as a safety measure

Reboot an Instance

Try a reboot before rescue for less severe issues

Console Access

Use the VNC console for out-of-band diagnostics

Troubleshooting

Resolve boot failures and rescue mode issues