Hello guys,
I tried to install CHR on the Hetzner cloud, based on https://wiki.mikrotik.com/wiki/Manual:CHR_Hetzner
but I get no hard drive found after reboot.
I tried many different versions with no success.
How can I fix this issue?
Hello,
thank you for reaching out to us. We just tried with the newest stable version 6.47.7 (https://download.mikrotik.com/routeros/6.47.7/chr-6.47.7.img.zip) and the above mentioned Hetzner manual and CX11 cloud VM and it worked as expected. Please try again.
Thanks for your reply,
I attached my steps and results.
Is there any mistake by me?
Try of=/dev/vda
If I remember correctly that helped me with Aruba Cloud.
Thanks
My disk located at /dev/sda
However, I tried vda but didn’t work.
Ok. Short googling tells that you need forced reboot at the end of procedure, not the “regular” one:
echo 1 > /proc/sys/kernel/sysrq
echo b > /proc/sysrq-trigger
From here (in Russian).
the same result, it can’t detect the disk.
Also, I tried the power cycle from the panel.
RouterOS v6 kernel does not support AMD EPYC CPU’s, please use CX instances (Intel Xeon based ones), instead of CPX instances which are using AMD EPYC
You can use v7 beta with the CPX instances:
It didn’t work with CX instances too…
This is V7 beta.
Did you try V6?
The same mistakes.
None of the old instructions on the Internet work. I tried 6 leading cloud operators yesterday, and none of them worked. By some miracle, with technical support, we launched one instance. It’s the same everywhere: the image doesn’t load.
Top cloud operators:
https://www.hetzner.com/
https://www.vultr.com/
https://ramnode.com/
https://www.digitalocean.com/
https://www.kamatera.com/
https://www.linode.com/
https://www.arubacloud.com/
https://virmach.com/
We wanted to buy about 100 licenses. Now we are wondering if it is necessary… judging by the answers in the forum, the manufacturer does not care about the problems. If they were interested in selling and developing the product, they would be able to keep it in normal working condition.
Example instructions:
https://wiki.mikrotik.com/wiki/Manual:CHR_Hetzner
https://community.hetzner.com/tutorials/mikrotik-chr-basic-setup
https://www.wirelessnetware.ca/blog/mikrotik-canada-install-mikrotik-routeros-on-a-vultr-vps/
https://www.youtube.com/watch?v=UkPzoEI7Xqs
The response of support operator team:
Hello,
Unfortunately this is an issue that Mikrotik will need to release an update to fix. Their kernel drivers do not support some of the virtualization technologies necessary for hosting in our infrastructure.
I am glad to hear that you have made this work.
Please let us know if you have any further questions regarding our infrastructure or platform.
System Administrator
Hello,There was an update to the underlying hypervisor that Mikrotik doesn’t have the latest drivers to support just yet. What you can do to install Mikrotik is to first install FreeBSD 13 from our Marketplace Apps, and when finished, mount your Mikrotik ISO image onto the Free BSD13 instance. The instance will reboot to the Mikrotik ISO image, which will now be able to see the disk drive and allow you to install the Mikrotik OS by overwriting FreeBSD 13.
FreeBSD 13 has the updated drivers installed in the VM definition file that the hypervisor uses to manage your VPS.
Regards,
System Administrator
Tested chr-6.49.1.img and chr-6.48.5.img versions
Thanks a lot for any help !
I was able to deploy MikroTik CHR on Hetzner just this last month actually without issues with booting during the CHR install itself.
In my case, the CHR runs in CentOS 8 Stream as KVM Guest on a Hetzner dedicated machine (with two WAN IP’s - one for the dedicated server, other for the CHR and network behind it) with AMD Ryzen 5 3600 CPU. Currently enjoying the benefits of the recently added ZeroTier One functionality actually.
Maybe the official guide works for VirtualBox, but it never worked for me on Qemu/KVM, what I did was the following:
[] Download the CHR Raw disk image from: https://mikrotik.com/download
[] Extract the archive
[] Convert the IMG to QCOW2 format
[] Resize the disk image to expand it’s size (best to do it initially, so that CHR automatically extends the system partition to all available disk space and you don’t have to resize it later)
wget https://download.mikrotik.com/routeros/7.1/chr-7.1.img.zip
unzip chr-7.1.img.zip
qemu-img convert -f raw -O qcow2 ./chr-7.1.img ./chr-7.1.qcow2
qemu-img resize ./chr-7.1.qcow2 +10G
And even tho, the latest CHR versions are suppose to be EFI compatible, I still used Legacy BIOS boot for VM config - EFI was never supported in any CHR 6.x version apart from Development/Testing channels. When running directly in the cloud, writing it directly to the disk might require setting up the boot flag too.