T

Julien LutranandClaude Opus 5 203728674f nuc: media over NFS from nas, on-demand role, i915 and input traps

nuc keeps only what needs its iGPU. blocky, privoxy and transmission-bt
moved to nas so the box can be powered off when not watching Jellyfin or
using the Spotify kiosk.

- /srv/media is now an NFSv4 mount from nas; jellyfin-server reads it
  with shift=false (idmapped mounts are unsupported on NFS, as the
  container doc already noted for CIFS) and readonly=true
- replication to nas is a systemd timer with Persistent=true, not cron —
  an on-demand host misses its 03:30 window and cron cannot catch up

Two failures documented in full, both diagnosed from the wrong layer
first:

- booting with the TV connected and powered on kills the i915 probe
  (drm_WARN_ON in intel_modeset_setup_hw_state), so /dev/dri never
  appears, snd_hda_intel deferred-probes forever holding the PCI device
  lock, and incusd blocks in sriov_numvfs_show — no container starts at
  all, including LAN DNS. Identical on 6.12.107 and 6.12.105.
- the kiosk input gid mismatch is real but was NOT the cause of the
  2026-08-30 outage (flat K400 batteries were); seatd opens input devices
  as root, so kiosk group membership is not on that path. Records the
  one-line raw capture that settles hardware-vs-software immediately.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-30 23:53:30 +02:00

archer-c7

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

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

ks2

ks2: ks4 pull leg and its WireGuard tunnel move from nuc to nas

2026-08-30 23:53:30 +02:00

ks4

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

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

nas

nas: new storage host on A1SAi-2750F — 4 TB off USB onto SATA

2026-08-30 23:53:30 +02:00

nuc

nuc: media over NFS from nas, on-demand role, i915 and input traps

2026-08-30 23:53:30 +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

nas: new storage host on A1SAi-2750F — 4 TB off USB onto SATA

2026-08-30 23:53:30 +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, iGPU instances
nas/ — storage + backup host nas (Supermicro A1SAi-2750F): the 4 TB on direct SATA, media over NFS, backup pools
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).