2 ms·
Hetzner's dedicated servers give you KVM access for stuff like tweaking your bios settings, installing an OS, or I guess using your boot menu. You have to reque
by wongarsu 3y ago
Hetzner's dedicated servers give you KVM access for stuff like tweaking your bios settings, installing an OS, or I guess using your boot menu. You have to request them via support ticket, but last time I did that I got it within 5 minutes, no questions asked.
If you have your own server in a rack somewhere chances are you bought one with a similar web interface (IMPI/BMC/whatever your brand calls it) on a separate always-on NIC on the mainboard.
https://docs.hetzner.com/robot/dedicated-server/maintainance/kvm-console/ https://docs.hetzner.com/robot/dedicated-server/maintainance...
- codetrotter 3y agoWhen I installed FreeBSD on my Hetzner servers, I did so by booting the servers into the Linux based rescue mode and then I think I used dd to write the mfsBSD media onto one of the hard drives. This way I didn’t have to request KVM access for my servers. Perhaps a similar method can be used in order to install ZFSBootMenu
- themoonisachees 3y agoNice tip but if you fail your server is toast and that's an interesting support ticket.
- codetrotter 3y agoTheir Linux based rescue mode boots from network. I should probably specify though that I do this when setting up a new server. If you fail then it should still be possible to select their Linux rescue image again from the Hetzner control panel and force reboot the server. I seem to recall that I had to try a couple of times before I got it right. And that I did exactly that; select their rescue image again and force reboot.
- wkat4242 3y agoNot a big deal though when you're doing a fresh install. Just cancel the server and provision a new one.
- numpad0 3y agorootfs should be network mounted by NIC feature on most clouds, so it should just be the matter of clicking "Force shutdown" and "Reset disk to default install"