UNRAID

[ehowton]

It wasn't really fun, or easy, or even really necessary if we're being honest. Mostly because UNRAID isn't much of a hypervisor, and I'm really not into that whole "Docker" thing - which looks freaking awesome if it like, worked and stuff. But I'm a sysadmin - I have needs. Things like access, and tools, and the ability to manipulate things outside their intended purpose. Dockers don't really have that. So I used VMs, but again, UNRAID is not much of a hypervisor which made things difficult. Geekfriend migrated her minecraft server from my R610 to her UNRAID, mostly because COX can eat a bag of dicks. That meant at some point, I'd likely poweroff the minecraft server. And really, the only things running on the ESX host are my bastion (openBSD) and my DNS server (rocky linux), neither of which require many resources. Figured running them on UNRAID would be non-impactful. What I didn't plan on doing was spending most of the day and all night getting something relatively easy to work. Enter the Story of my Life.

Anyway, upgraded openBSD from 6.6 to 7.5 while I was at it, and traded in rocky linux for openSUSE 15.6. What gave me the most difficulty was qemu, which UNRAID runs as it's built-in hypervisor, so I was unfamiliar with....well, just about everything.

Anyway, its done. I have a 14TB drive arriving tomorrow, which is going to be a huge pain in the ass because your parity drive has to be the largest one (the reason I only bought 12TB drives for so long) and migrating that much data is a pain in the ass. Just in case (and because Geekfriend did it also) I'm upgrading from 16GB of RAM to 64GB because running Dockers and VMs requires more than just idling storage - the idea being, I've managed to consolidate my entire homelab into a single box I could lift and ship at a moment's notice.

We'll see.