These all start the same way: start rescue mode and log in. Run mship-disks first to check it can see your system.
The most useful thing to understand is mship-chroot. It mounts your system and gives you a shell inside it, so that commands act on your system rather than rescue. Type exit to come back. Your system stays mounted until you run mship-unmount.
When you've finished, always run mship-unmount, and then press Exit rescue and boot from disk on the Boot tab.
Forgotten your password
mship-password ubuntu
Use your own username, or leave it off to set root's. Type the new password twice.
This password works at the console. Cloud images usually keep password login over SSH turned off, so add a key too if that's how you connect.
Lost your key
Your new key goes on your own system. First make one with PuTTYgen and copy the line starting ssh-ed25519. Then:
mship-chroot
su - ubuntu
mkdir -p ~/.ssh && chmod 700 ~/.ssh
echo 'ssh-ed25519 AAAA...your key... my-desktop' >> ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys
exit
exit
mship-unmount
Use your own username in place of ubuntu. The first exit leaves your user, and the second leaves your system.
The VM won't boot after a bad fstab change
A line in /etc/fstab for a disk that isn't there can stop a system from starting. This is common after removing a disk.
mship-chroot
nano /etc/fstab
Put # in front of the bad line to disable it. For a disk you might remove again, add nofail to its options, which stops a missing disk from blocking the boot. Then save with Ctrl+O and Enter, leave with Ctrl+X, and type exit.
The VM stops at the bootloader, or says no bootable disk
mship-grub
This reinstalls the bootloader using your system's own GRUB, and rebuilds its menu. Exit rescue to try it.
If a kernel update went wrong, you may also need to rebuild its startup files. On Debian and Ubuntu:
mship-chroot update-initramfs -u -k all
On AlmaLinux and Rocky:
mship-chroot dracut --regenerate-all --force
Filesystem errors
If the console showed filesystem errors, or the VM was forced off and now won't start:
mship-unmount
mship-fsck
This only looks, and it lists any problems. If it finds some, fix them with:
mship-fsck --repair
Filesystems that are mounted get skipped, which is why mship-unmount comes first. Take a copy of anything important before you repair, if you can, as a repair can remove damaged files. It handles ext4, xfs, btrfs and vfat.
The disk is full
A completely full disk can stop a system from starting or logging anyone in.
mship-chroot
df -h
du -xh / --max-depth=2 | sort -h | tail -20
Old logs are often the culprit. journalctl --vacuum-size=100M trims the system journal, and on Debian and Ubuntu, apt-get clean clears the package cache. Be careful what else you delete.
If you just need more room, grow the disk from the Storage tab, and let the system grow into it at the next boot.
A firewall or network change locked you out
First check the firewall rules on the panel, which you can change with no rescue needed. If the problem is inside your system:
To switch off ufw, edit its settings and change ENABLED=yes to ENABLED=no:
mship-chroot nano /etc/ufw/ufw.conf
To switch off firewalld:
mship-chroot systemctl disable firewalld
If you've broken your network settings, the easiest fix is usually to let cloud-init write them again from the panel's details:
mship-cloudinit
At the next boot, it sets up your network, user and SSH keys again as it did when the VM was built. Expect new SSH host keys, so PuTTY will warn you once.
Get your data off
Rescue has internet access, so you can send files from it to another machine you control. Your system has to be mounted first:
mship-chroot true
rsync -avP /mnt/os/home/ [email protected]:vm-backup/
mship-chroot true is a quick way to mount your system at /mnt/os without staying inside it. Run long copies in tmux, so they survive if your connection drops. To send one file somewhere web-based, curl is there too.
Your VM can't send to private addresses outside its project, so the other machine needs a public address. Peered projects are the exception.
Before you make big changes
A backup is the only true undo. If the VM can still be backed up, take one before a repair that might go wrong.
Still stuck?
Rescue is yours to use however you like. You have a full shell with root, and your disks are right there. We can't fix what's on your VM for you, but you can always rescue your data and start again with a clean install.