I’ve got yet another Inter-Tech rack mountable server case. I really wanted a few hot swappable disk bays in the front, and buying two removable 4-drive backplanes were more expensive than getting a new case 😮

So I sold the 4U-4129-N and moved Alpha into this case instead 🙂

A few days ago; sitting outside — drinking coffee and minding my own business, I received an email from my UPS:

Utility power not available.

2021/06/01 18:38:27

My homelab had lost both power sources 😮 This whole area had a power outage — a good opportunity to do a UPS and power down test 😛

I moved my main hypervisor, Alpha, into a new server case; a compact Inter-Tech with 8 hot-swappable bays in the front.

I also moved the four SSDs over from the failed ZFS SSD pool project, and this time it worked! 😃

One (potential) downside to running public services on your homelab, is that you expose your IP address. That may, or may not, be a problem — but here are ways around it. The simplest way is to put Cloudflare in front, but this will only handle web traffic, and is a bit of a black box.

Another, more hands-on, approach is to use a VPS (or LXC container); WireGuard and iptables. We will create a secure tunnel between the VPS/container and the homelab HAProxy instance, and forward traffic using iptables.

This post was suppose to be a “look I made an SSD ZFS pool”, but will instead be the first post in a trouble-shooting series. Trying to get my SSDs to behave.

But — I am getting ahead of myself… Let’s start at the beginning.