From one tower to three mini PCs
Chapter 1 of five: why three nodes instead of one, the machines, and Proxmox VE 9 with a VLAN-aware bridge on each.
Until this spring everything in the loft ran on one tower: a ten-year-old desktop with Proxmox, 32 GB and a fan you could hear from the stairs. It drew about 120 watts doing nothing, and every kernel update took Home Assistant, Jellyfin and the house’s DNS down with it. This series replaces it with three mini PCs in a Proxmox cluster, the NAS as shared storage, nightly backups and one Ansible repository for all of it.
Why three
Two nodes cannot outvote each other: when one goes down, the other loses quorum and will not start guests. Three can lose one and carry on. Three small ones also cost less than one large one with the same memory, and each draws about 7 watts at idle.
The machines
| Name | CPU | Memory | Disk | Address |
|---|---|---|---|---|
| pve-1 | Intel N100 | 16 GB | 512 GB NVMe | 10.0.10.11 |
| pve-2 | Intel N100 | 16 GB | 512 GB NVMe | 10.0.10.12 |
| pve-3 | Intel N100 | 16 GB | 512 GB NVMe | 10.0.10.13 |
16 GB is the most the N100 takes. It is enough for the guests I run, with room for two nodes to carry the third’s guests during an update.
Install Proxmox VE 9
The installer goes on a USB stick. Check the device name twice, because dd writes to whatever you give it.
$ lsblk -d -o NAME,SIZE,TRAN
NAME SIZE TRAN
sdb 14.6G usb
nvme0n1 476.9G nvme
$ sudo dd if=proxmox-ve_9.0-1.iso of=/dev/sdb bs=4M status=progress conv=fsyncIn the installer each node gets its name and a fixed address, with the router at 10.0.10.1 as gateway. I chose ext4 on the single NVMe disk. ZFS wants more memory than I want to give it.
A bridge that knows VLANs
The installer creates vmbr0 on the network port. I made it VLAN-aware from the start, so guests can be tagged later without touching every node again.
auto vmbr0
iface vmbr0 inet static
address 10.0.10.11/24
gateway 10.0.10.1
bridge-ports enp1s0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes # [!code ++]
bridge-vids 2-4094 # [!code ++]ifreload -a applies it without a reboot. Next chapter joins the three into one cluster and moves the guests off the tower.
subscribe
New entries and the next chapter by mail, nothing else.