T

Julien LutranandClaude Fable 5 058833470b nuc: second dropout rules out the cable; add the pool-health watchdog

Aug 29 16:22 the enclosure dropped again despite the new cable, pool
suspended, and ZED sent nothing (suspended pools keep the vdev ONLINE;
data-class events were muted). Enclosure replacement is now the prime
candidate and a gate before the pool hosts the ks4 off-site leg.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-30 00:33:29 +02:00

archer-c7

plakar-s3-data: seed done except seafile-fs (EINTR livelock, excluded)

2026-08-24 00:07:01 +02:00

ks2

docs: restore drill passed — S3 leg gate closed

2026-08-28 19:16:02 +02:00

ks4

docs: record the measured steady-state nightly (1.24 TiB walked in 1m43s)

2026-08-29 05:10:01 +02:00

nuc

nuc: second dropout rules out the cable; add the pool-health watchdog

2026-08-30 00:33:29 +02:00

backup-strategy.md

backup-strategy: note the measured nightly cost

2026-08-29 05:10:15 +02:00

new-container.md

doc: instance leg to S3 shelved; ks2 push is the interim off-site leg

2026-08-28 16:17:11 +02:00

README.md

doc: split per-host READMEs, gitea cross-repo links, consistency pass

2026-08-28 16:04:07 +02:00

README.md

Personal infrastructure notes

Two repositories back this setup: doc (this one) and scripts (the cron drivers and their config files, deployed to /root/scripts on each host).

Start here:

backup-strategy.md — what is backed up, by which tool, on what schedule, and how to restore.
new-container.md — conventions for adding a service to ks4 (and getting it backed up automatically).

Tech notes

nuc/ — home lab on nuc: host, storage, instances
ks4/ — prod server ks4 at OVH: host, services, network flows
ks2/ — legacy backup server being decommissioned
archer-c7/ — home router (TP-Link Archer C7 v5 running on OpenWrt)

Conventions

One markdown file per topic in the correct subdir, containing the full implementation notes, configuration, and troubleshooting notes.
Containers are built from Debian/Ubuntu images and configured exclusively through incus exec/incus config so the doc is the single source of truth — rebuilding = re-running the script.
Adding a service to ks4: follow new-container.md (no Docker in containers — incus runs OCI images natively and incus-compose handles stacks; data paths go into scripts/restic-paths).