Hardware

Every hardware guide on this site so far has assumed the rack already exists. Buying used enterprise gear, sizing a UPS, picking a managed switch, all of it takes for granted that there’s somewhere to physically put the thing. That assumption falls apart fast for anyone starting from a mini PC on a shelf and a switch zip-tied to the underside of a desk. This is the article that comes before all of those: the cabinet itself, the rails that hold gear in it, the power distribution feeding it, and the cable management that decides whether adding a fourth device is a five-minute job or an afternoon of re-routing everything you already installed. ...

Every homelab ends up with SSDs doing several different jobs at once: booting the hypervisor, holding VM disks, backing a ZFS special vdev or SLOG, maybe just serving as bulk fast storage for a database. Most buying advice treats this as one decision, “get an SSD, more capacity is better,” and stops there. That’s fine for a boot drive. It’s a real mistake for anything doing sustained writes, and it can quietly cost you data integrity on a ZFS log device. The differences between consumer and enterprise flash are specific and they map directly onto which job a drive should actually do. ...

Most homelab buying guides start with the case or the drives, but the CPU and motherboard decide almost everything downstream of them. PCIe lane count sets how many cards you can run at once. ECC support decides whether a bit flip in RAM silently corrupts your ZFS pool or gets caught and corrected. IOMMU group layout decides whether GPU or HBA passthrough to a VM is a ten-minute config change or a wall you can’t get past no matter what you try. None of that shows up on a spec sheet the way clock speed and core count do, which is exactly why it gets skipped over until someone hits it the hard way. ...

Every homelab guide eventually tells you to “get a managed switch,” usually without saying why, or which one, or what happens if you buy the wrong one. This site has already covered when 10GbE is worth the upgrade and how to configure VLANs, bridges, and bonding once you’re inside Proxmox. This article is the piece that comes before both of those: picking the actual switch hardware sitting between your gear, the decision that either makes everything downstream easy or makes you fight your network for the next three years. ...

A UPS without a way to talk to your hosts is just an expensive surge protector with a battery in it. It’ll keep the lights on for a few minutes, but the moment that battery runs out, every VM and container you’re running goes down exactly as hard as it would have without a UPS at all, just a little later. The part that actually protects you, a UPS that tells your hosts “power’s out, shut down now while you still can,” is a separate piece of software most people never get around to setting up. Here’s how to size the UPS itself, and how to wire up Network UPS Tools (NUT) so an outage ends in a clean shutdown instead of a dirty one. ...

Most homelab hardware guides stop at “buy it, rack it, install Proxmox.” The thing that actually changes how a homelab feels to run day to day is whether you can reach the machine when the OS won’t boot, the network stack is misconfigured, or the box is three rooms away in a closet with no monitor attached. That’s what out-of-band management is for, and if you’re running used enterprise gear, you almost certainly already own it. Most people never turn it on. ...

Every data hoarder eventually hits the same wall: the motherboard only has six SATA ports, and the build calls for twelve drives. The instinctive fix is a cheap RAID card off eBay, and that instinct is almost always wrong. The actual answer, in nearly every homelab storage build, is an HBA flashed to IT mode. Here’s what that means, why it matters, and how to do it without turning a $40 card into a paperweight. ...

RAM is one of the easiest specs to either badly underbuy or badly overbuy in a homelab, because the honest answer to “how much do I need” is “it depends on what you’re actually running,” and most buying guides dodge that and just tell you to get 32GB or 64GB and move on. That’s not wrong exactly, but it skips the reasoning that lets you size correctly for your own setup instead of someone else’s. Here’s how to actually work it out, plus the ECC question that comes up right behind it. ...

“Do I need a GPU for this” comes up constantly in homelab planning, usually attached to one of two very different goals: hardware-accelerated transcoding for Plex or Jellyfin, or running local AI workloads like Ollama or Stable Diffusion. Those two goals point at completely different hardware, and buying for one when you actually need the other is one of the more common expensive mistakes in this hobby. Here’s how to figure out which category you’re actually in before you spend anything. ...

Ask “what should I run Proxmox on” in any homelab community and you’ll get two camps talking past each other, one pushing a mini PC (an Intel NUC-style box, a Beelink, a Minisforum), the other pushing a custom build in a real case with expansion slots. Both are right, for different homelabs. The question isn’t which is objectively better, it’s which set of tradeoffs actually matches what you’re going to do with the box. ...