Homelab server: a quiet, efficient server for home

A homelab is a small data centre at home: for learning, experimenting and running services you would rather host yourself than in the cloud. Used enterprise hardware brings ECC memory, remote management and plenty of drive bays at a fraction of the original price. To keep a home server from becoming a nuisance, mind form factor, noise and power draw.

What a homelab server is good for

• Learning: try out Linux, networking, Active Directory or Kubernetes without putting production systems at risk.
• Virtualisation: Proxmox VE runs many VMs and containers on a single host.
• NAS and backup: a ZFS pool under TrueNAS keeps photos, documents and the backups of every device.
• Self-hosting: file sync, a password manager, a DNS ad blocker or your own VPN access.
• Home automation and media: Home Assistant, camera recording or a media server.

Homelab hardware: MicroServer, tower or rack?

Form factor decides everyday usability more than any CPU. The HPE MicroServer Gen10 Plus is very compact, with four 3.5-inch bays, one PCIe slot and an external 180 W power supply. Tower servers such as the Dell T440, HPE ML350 Gen10 or Dell T630 offer eight bays, two CPU sockets and several full-size PCIe slots. The T630 is a generation older (Xeon E5 v3/v4) and idles a little higher, but has 24 DIMM slots. Rack servers are cheapest but built for ventilated cabinets.

Noise: making a home server quieter

1U servers cool with small 40 mm fans at high speed and are clearly audible even at idle. 2U servers use larger fans and are quieter; towers are the quietest. Every server spins its fans to maximum briefly at power-on – that is normal.

• Cooling profile: the BIOS or the BMC (iDRAC, iLO, IPMI) usually offers a profile with lower fan speeds.
• Fewer drives: every hard drive adds heat and noise. Two large drives are quieter than six small ones.
• Air front and back: in a warm, closed cupboard the fans run high all the time.

Power consumption: idle is what counts

A homelab server runs around the clock, mostly at idle. The maths is simple: power × 8,760 hours gives the annual consumption. At an assumed 30 cents per kWh, a server idling at 100 W uses 100 W × 8,760 h = 876 kWh, about €263 a year. Every watt saved is worth a good €2.60, so a 35 W MicroServer instead of a 110 W dual-socket tower saves about €197 a year.

How to cut consumption

• One CPU instead of two: the second socket and its memory often cost 15–30 W at idle. 8–16 cores are plenty for most homelabs.
• Few, large DIMMs: four 32 GB modules draw less than sixteen 8 GB modules.
• SSDs instead of hard drives: a 3.5-inch drive draws 4–8 W at idle, a SATA SSD 1–2 W.
• Switch off what you don't use: disable unused onboard NICs and controllers in the BIOS and remove surplus PCIe cards.
• BIOS power profile: power-saving profiles with deep C-states lower idle draw noticeably; pure performance profiles keep the CPU awake.

Storage: an HBA in IT mode for TrueNAS and ZFS

ZFS – the file system behind TrueNAS and an option in Proxmox – wants to see the drives directly: SMART data, error reports, write cache. A RAID controller gets in the way, so ZFS needs an HBA in IT mode, such as the LSI 9300-8i or the Dell HBA330. Both pass eight SAS or SATA drives straight to the operating system, and more via an expander backplane.

If you prefer classic hardware RAID, for example for Windows Server, our guide RAID levels compared explains the differences. Controllers and HBAs are listed under RAID controllers.

Networking: 10 GbE in the homelab

Once a NAS has several drives or SSDs, 1 GbE at around 115 MB/s becomes the bottleneck. Used 10 GbE cards are cheap: the Intel X520-DA2 is a proven classic with two SFP+ ports, the Intel X710-DA2 the more modern, more frugal PCIe 3.0 option. The Mellanox ConnectX-3 Pro offers 40 GbE via QSFP+, also runs at 10 GbE with an adapter, and its driver is part of the Linux kernel.

For short runs, SFP+ direct-attach cables (DAC) are cheaper and use less power than 10GBASE-T over copper. Two servers can also be linked directly without a switch, for fast backups for instance. Some Intel cards only accept certain SFP+ modules, depending on firmware and driver. More models are listed under network cards.

Starter configurations: small, medium, large

If TrueNAS runs as a VM under Proxmox, pass through the whole HBA, not individual drives. For a GPU for transcoding or local language models, see our guide AI servers for local LLMs.

Software: Proxmox VE, TrueNAS and Docker

Proxmox VE is the best base for most homelabs: VMs and Linux containers through a web interface, ZFS included, usable without licence fees, with optional support subscriptions. TrueNAS is the first choice when storage is the focus. Docker with Compose files is the quickest way to individual services, for example in a lean VM. Our guide Proxmox instead of VMware explains why many admins are switching. Licence terms change, so check the current position with the vendor.

Rack or no rack?

A single tower does not need a rack. Once a switch, patch panel, UPS and one or two rack servers come together, a cabinet brings order and short cable runs. Watch the depth: a 2U server such as the Dell R740 is around 70 cm deep, so plan a cabinet 1,000 mm deep. Shallow wall-mount and network cabinets of 450–600 mm will not fit. A small UPS bridges short outages and shuts the servers down cleanly. A rack only dampens noise if it is explicitly soundproofed. More in our 19-inch rack guide.