Rescue Mode
Recover servers and instances using rescue mode and IPMI access
Rescue Mode
Rescue mode provides emergency access to servers and instances when normal access is unavailable. It is useful for recovering from misconfigurations, failed upgrades, or filesystem corruption.
When to Use Rescue Mode
- Lost SSH access due to firewall misconfiguration
- Failed OS upgrade or kernel panic
- Filesystem corruption preventing boot
- Network configuration errors
- Recovering data before reinstallation
Rescue Mode for Instances
Virtual machines can be booted into a rescue environment via the instance action API.
Via API
curl -X POST https://api.fugoku.com/v1/instances/inst-abc123/action \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"action": "rescue"
}'The instance will reboot into a rescue environment. SSH credentials are provided in the instance details.
Via Console
- Navigate to Compute → Instances
- Select your instance
- Click Actions → Rescue Mode
- Confirm the action
The instance will reboot into the rescue environment. Connection details are displayed on the instance page.
IPMI Access for Bare Metal Servers
Bare metal servers provide out-of-band management via IPMI (Intelligent Platform Management Interface). IPMI allows you to access the server console, power cycle, and boot from ISO images regardless of the server's OS state.
IPMI Features
- Serial console — access the server console over SSH
- Power management — power on, off, and reset
- Boot from ISO — boot from a rescue ISO or custom image
- Sensor monitoring — temperature, fan speed, voltage
Accessing IPMI
IPMI details are available in the server response:
GET /v1/servers/srv-abc123The response includes:
{
"data": {
"id": "srv-abc123",
"type": "servers",
"attributes": {
"ipmi_status": "Normal",
"rescue_allowed": true,
"interfaces": [
{
"role": "ipmi",
"name": "IPMI",
"mac_address": "00:11:22:33:44:55",
"description": "IPMI Interface"
}
]
}
}
}Rescue Mode for Bare Metal
Bare metal servers support rescue mode through the provider's rescue functionality. Check if rescue is allowed:
curl https://api.fugoku.com/v1/servers/srv-abc123 \
-H "Authorization: Bearer $TOKEN"If rescue_allowed is true, you can trigger rescue mode via the server action:
curl -X POST https://api.fugoku.com/v1/servers/srv-abc123/actions \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"data": {
"type": "actions",
"attributes": {
"action": "rescue"
}
}
}'Via Console
- Navigate to Compute → Servers
- Select your bare metal server
- Click Actions → Rescue Mode
- Confirm the action
The server will boot into a rescue environment. SSH and serial console access details will be displayed.
Exiting Rescue Mode
After recovering your data or fixing the issue, you can exit rescue mode and reboot into the normal OS:
curl -X POST https://api.fugoku.com/v1/instances/inst-abc123/action \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"action": "reboot"
}'Or via the Console: Actions → Reboot.
Best Practices
- Always create a backup before performing rescue or reinstallation
- Rescue mode is temporary — exit it as soon as recovery is complete
- Use IPMI serial console for low-level troubleshooting
- For persistent issues, consider using Reinstall to restore the original OS image