How do I use rescue access when my VPS will not boot?
A recovery console can show boot failures even when SSH is unavailable. A supported rescue ISO may provide a separate operating system from which authorised administrators inspect the guest’s disks. Attaching an ISO and reinstalling the server are different actions.
Instructions
1. Confirm the supported recovery path
In Britixo, select the correct VPS and review Access or Recovery. Use the offered console or Attach ISO action only when available, reading the required fields and impact. Do not choose Reinstall merely to obtain a rescue shell.
2. Identify the environment and disk layout
Once in a Linux rescue environment, inspect before mounting or repairing anything.
uname -r
lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS
findmnt -o TARGET,SOURCE,FSTYPEThe running kernel and root filesystem may belong to the rescue image, not the installed VPS. Device names can differ from normal boot.
3. Follow the precise recovery procedure
Use the installed system’s filesystem and bootloader documentation for the identified layout. Avoid formatting, blind filesystem repair or guessed mount commands. After a successful repair, detach the rescue image if required and verify normal boot and application operation.
Check the result
- The correct guest disks are identified independently of the rescue image.
- Normal boot succeeds after the supported recovery process and required applications are healthy.
Troubleshooting
- The rescue environment cannot see the disk
- Confirm that the provider attached the intended volume and that the rescue image supports its virtual controller.
- The server keeps booting into the ISO
- Check the documented detach and boot-order workflow after recovery is complete.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.