(You must already be logged in to Gitlab or you’ll hit a 404)
This page will help you fix your Bytemark host, assuming it is running a Linux-based OS. We assume you’ve been able to follow the instructions on how to boot your server over the network or boot your legacy VM in rescue mode.
If you have a Dedicated Server, the first thing you will want to do is type:
mount /dev/md1 /target mount /dev/md0 /target/boot
(For premium machines with hardware RAID, or some non-standard software RAID configurations the device names will differ. Contact support if you are unsure.)
For our Cloud Servers, this will be:
mkdir /target mount /dev/vda2 /target mount /dev/vda1 /target/boot
which will assemble your normal filesystem on
Legacy virtual machine customers should type:
mount / -o rw,remount
to be able to change files as normal.
You are then free to edit any files, which may be all you need to do to fix your problem. If that’s all you need, just type
reboot when you’re done and wait for your system to boot up normally.
If you have a virtual machine and need to get files on or off the rescued system, you may want to start your networking with:
If you need to copy files on or off your server, you should start an SSH server:
On a Dedicated Server you should also set a root password with
passwd (this does not affect your normal root password) and be prepared to click through a host-key warning when you connect.
You can then use SCP or SFTP to copy files on and off the server as root - the server should have its normal IP address.
This step isn’t necessary for Legacy Virtual Machine customers.
On a Dedicated Server, if you need to run programs on your real file system, type:
This will leave you at a prompt “inside” your normal system. You can use this to re-run
grub. When you’re finished, you will probably need to type
exit before you can issue the reboot command.
Probably the most common operation that you can do is resetting your root password. While inside the system you can run:
and set yourself a new root password.