Homelab

Style guide: how an entry here looks

Every element an entry on The Loft Rack can use, written the way Edda and I write them.

Edda asked how an entry should look before she wrote her first one. This is the answer: every element an entry here can use, each under a heading that names it.

Heading level two

Sections a reader jumps to, such as "The timer". They fill the table of contents.

Heading level three

A step inside a section. Indented in the table of contents.

Heading level four

Rare. Used once, for the options of one config key.

Heading level five

Not used yet.

Heading level six

Not used yet either, but it has a size.

Paragraph with inline formats

The rack draws 62.5 watts, on average, and the old tower is gone. Commands go in code, like restic snapshots. The NAS keeps four disks, rated for Tmax = 60 °C, and a TiB is 240 bytes. In November the alert went to an address I no longer read, as the incident note explains.

Bulleted list

  • Three nodes, one cluster.
  • One NAS with four disks.
  • One Pi that only does DNS.

Numbered list

  1. Check last night’s backup.
  2. Update one node.
  3. Wait for quorum, then the next.

Blockquote

A backup counts once a restore has worked.

Aside quote

Edda’s rule for the loft: nothing goes up the ladder that cannot be switched off over the network.

Code block with a file name

services:
  jellyfin:
    image: jellyfin/jellyfin:10.10.7
    restart: unless-stopped

Terminal

$ pvecm status | grep Flags
Flags:            Quorate
$ df -h /srv
Filesystem      Size  Used Avail Use% Mounted on
/dev/md0        7.3T  4.1T  2.8T  60% /srv

Diff

--- a/etc/default/grub
+++ b/etc/default/grub
@@ -9 +9 @@
-GRUB_CMDLINE_LINUX_DEFAULT="quiet"
+GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"

Marked, added and removed lines

ansible_user: root # [!code highlight]
restic_repo: sftp:restic@nas:/srv/restic # [!code --]
restic_repository: sftp:restic@nas:/srv/restic # [!code ++]

Tabs

$ sudo apt install restic
$ sudo dnf install restic
$ sudo apk add restic

Long block, folded

- name: Install NUT
  ansible.builtin.apt:
    name: nut

- name: Set the mode
  ansible.builtin.lineinfile:
    path: /etc/nut/nut.conf
    regexp: ^MODE=
    line: "MODE={{ nut_mode }}"

- name: Describe the UPS
  ansible.builtin.template:
    src: ups.conf.j2
    dest: /etc/nut/ups.conf
  when: nut_mode == "netserver"

- name: Start the driver and the monitor
  ansible.builtin.systemd_service:
    name: "{{ item }}"
    enabled: true
    state: started
  loop: [nut-driver.target, nut-monitor.service]

Wrapped lines

[Service]
Type=oneshot
ExecStart=/usr/local/bin/restic-check.sh
Environment=RESTIC_PASSWORD_FILE=/root/.restic-password RESTIC_CACHE_DIR=/var/cache/restic GOMAXPROCS=2

Code with a caption

$ pvesm set nas-dump --prune-backups keep-last=3
Run on one node, valid on all three, since the night the NAS filled up.

Horizontal rule

Separates a postscript from the entry.


Image, regular width

An editor with compose.yaml for Jellyfin 10.10.7 and /dev/dri passed in.
compose.yaml in the media container on pve-3.
A line chart of the rack’s power draw over a week, before and after the mini PCs.
From about 150 to about 62 watts. The image links to the entry with the numbers.

Image, wide

A diagram of the loft network: modem, opnsense, switch, the three nodes, the NAS and the Wi-Fi.
The network after the VLAN weekend.

Image, full width

Dark chart paper with the prompt ~/loft $ and the line: Three mini PCs, a NAS and what broke this week.
The prompt this journal is named after.

Callouts

Note, tip, warning and danger take the colours of the code. The others follow Ghost’s callout colours.

ℹ️
Every address here is on VLAN 10, 10.0.10.0/24.
✅
Restore one file after every change to the backup script.
⚠️
Update one node at a time. With two rebooting at once, the third loses quorum.
🛑
dd writes to whatever device you give it. Check the name with lsblk first.
📎
Every config file in these entries is in loft-ansible.
🧾
Watts come from the smart plug at the rack’s socket, as daily averages.
🎂
The cluster turned six months old on 2026-11-10.
🧪
New software runs on the sandbox VM on VLAN 20 first.
📬
The log by mail goes out on the first of the month.

Toggle

Why Proxmox and not plain Docker?

Home Assistant wants a whole VM, and live migration needs a hypervisor. Docker still runs inside the containers that want it.

Why RAID 10 on the NAS?

A rebuild reads one disk instead of all of them. The cost is half the space.

Bookmark

loft-ansible
Ansible roles for three Proxmox nodes, a NAS and a UPS in a loft.
The repository, one tag per release.

A second bookmark

loft-ansible releases
Every version with its notes, from v1.0.0 to the inventory in YAML.

Button

Button, centred

Header card

Rebuilding the rack

Five chapters from one old tower to a cluster of three.

Start with chapter 1

Header card, split with image

loft-ansible v2.0.0

One inventory in YAML, and alerts that reach someone.

Read the release notes

Header card, centred

62.5 watts

The whole rack, on average, in October 2026.

Signup card

Call to action

SPONSORED

The loft costs 175 euros a year in power. Supporters pay part of it.

Chip in

Call to action for members

Only members see the card under this heading. Sign in and it shows up here.

Product

The N100 mini PC

Four cores, 16 GB, about 7 watts at idle. Three of them run the cluster.

Read why three

Audio

audio-thumbnail
The loft at night
0:00
/10

Video

0:00
/0:06
The rack with its switch blinking.

Looping video

0:00
/0:06

File

Embed

nas: /srv 60 % used, last snapshot 04:00, all three nodes quorate.

The status page on the NAS, embedded.

HTML card with a table

NodeGuestsIdle draw
pve-127 W
pve-227 W
pve-317 W

Markdown card with a table

Command What it does
pvecm status shows quorum
restic snapshots lists the backups

Typesetting

The first paragraph of an entry is set larger. These entries show the other variants:

Members pages

Readers who sign up meet four pages: Sign up, Sign in, Account and Pricing.

Comments

Buy Logbuch