SHIPPEDinfrastructure

Proxmox Server

One Proxmox node in the house that everything self-hosted runs on: a consumer board, a 4-core APU, a mergerfs and SnapRAID media pool, and eighteen months of crashes that turned out to be the RAM.

CREATED FEB 19, 2025 · UPDATED OCT 31, 2026

PROBLEM

Every experiment that needed somewhere to run got its own cloud account and its own way of being forgotten. The ones that mattered most were exactly the ones that should not have been rented.

HYPOTHESIS

One hypervisor at home makes a new environment free at the margin, and free at the margin is what decides whether an idea gets tried at all.

ARCHITECTURE

A single node, not a cluster: a B450 board with a 4-core, 8-thread APU whose integrated GPU is passed through to the Plex container for hardware transcode. The OS and guests live on NVMe. Media sits on four spinning disks pooled with mergerfs, with one disk given over to SnapRAID parity. Samba exports the pool to the house. Guests are backed up with vzdump to the parity disk, so backups add no sync load, and the host's own configuration goes into a nightly tarball, because vzdump backs up guests and nothing else.

STACK

Proxmox VEDebianLXCmergerfsSnapRAIDPlex

RESULT

Running, and finally boring. For eighteen months the host locked up hard every five to eight days and needed a physical power cycle. The cause was failing non-ECC memory, the evidence had been in the kernel log the whole time, and nobody saw it because every alert the box sent was queued behind a masked mail service. The full story is in the postmortem note.

LEARNINGS

  • A backup nobody has restored from is a hypothesis, not a backup.
  • If the box cannot tell you it is failing, it is failing silently. Alerting is part of the system, not a nice-to-have.
  • Non-ECC memory can corrupt for a year and a half without a single machine check exception.

PROVENANCE

Diagnosed and fixed over a long session with Claude Code on the host, every finding filed as a Linear issue with the evidence pasted in.

TAGS

homelabvirtualizationself-hostedbackupspostmortem