Our customers have reported some issues with Hetzner dedicated servers. The servers need special configuration to work smoothly with Virtkick and here's a short guide explaining how to do it.

1. Boot to rescue mode

First, you will need to boot your server into rescue mode, this can be done through the Hetzner control panel. After this has been done, enter the following commands:

fdisk -l 

Note the name of your primary disk and then execute:

mount /dev/DEVICE /mnt

Be sure to substitute DEVICE for the name you found by running fdisk -l.

Next, execute the following commands:

mount -t proc none /mnt/proc
mount -o bind /dev /mnt/dev
mount -t sysfs sys /mnt/sys
chroot /mnt/ /bin/bash

You should now be all set to proceed on to step two.

2. Correct networking problems

Second, you will need to edit your grub configuration to ensure this problem does not happen again. To do this, edit /etc/default/grub and add net.ifnames=0 to GRUB_CMDLINE_LINUX=, if you have other things there add the new line at the end of existing parameters.

Once you are done, your GRUB_CMDLINE_LINUX line should look something like this:

GRUB_CMDLINE_LINUX="nomodeset rd.auto=1 crashkernel=auto net.ifnames=0"

If your line looks similar to the line above you are all set to rebuild your grub config by executing:

grub2-mkconfig > /boot/grub2/grub.cfg

Your grub configuration should now have the necessary parameters to correct the networking problem.

3. Clean up

Finally, you'll need to exit your chroot by running the exit command. Next, unmount all of the things we mounted earlier by running:

cd; umount /mnt/proc /dev /mnt/dev /mnt/sys /mnt/

Once everything has been unmounted, set your server to boot into the standard mode (not rescue mode) and then execute the reboot command.

Your server should now boot up normally with networking enabled.

Have any problems? Let us know - we are happy to help!

Back to the list »

comments powered by Disqus