Documentationchevron_rightTroubleshooting

Troubleshooting · 6 min read

My VPS is not booting

Diagnose and fix boot failures including kernel panics, filesystem errors, and misconfigured bootloaders.

Last updated April 3, 2026

Step 1 — Check the VNC console

The VNC console shows the raw boot output, including any error messages that SSH would hide. Go to Instances → Manage → VNC Console.

Common messages and their meanings:

MessageCause
GRUB rescue>Bootloader can't find the kernel
kernel panic — VFS: Unable to mount root fsRoot filesystem corruption
fsck died with exit status 4Filesystem check failed
emergency modeSystemd fell back to rescue mode

Step 2 — Emergency mode (systemd)

If the VPS drops to emergency mode, log in using the root password via VNC and run:

journalctl -xb    # view boot log

Look for unit failures in the output. If it's a failed service:

systemctl status failing-service.service

Disable it to allow the system to boot normally:

systemctl disable failing-service.service
reboot

Step 3 — Filesystem check

If you see filesystem errors:

# From the VNC console in emergency mode
fsck -y /dev/vda1    # replace with your root partition
reboot

Step 4 — Bootloader issues

If GRUB is broken, contact support immediately — fixing the bootloader may require a rescue environment that we can mount for you.

Step 5 — Power cycle

Sometimes a hard power cycle resolves a stuck boot:

  1. In the control panel, click Power Off (hard stop).
  2. Wait 10 seconds.
  3. Click Start.

Still not booting?

Open a support ticket with:

  • A screenshot or copy of the VNC console output
  • Any recent changes you made (kernel update, package install, config edit)
  • Time the issue started

Related

Still stuck? Customers get support from the dashboard, and anyone can open a ticket. If you are not a customer yet, VPS plans deploy in minutes with root access and a browser console.

See VPS pricing