Files

T

Julien LutranandClaude Fable 5 ef88ef9342 docs: follow the storage move from nuc/USB to nas/SATA

backup-strategy (the entry point) still described nuc pulling the ks4
replicas: the leg, its WireGuard peer and the target pool now live on
nas with the 4 TB on direct SATA. Also: ks4 README flow chart redrawn
for the new topology, incus-copy leg 2 retargeted, usb4t-dropouts
marked RESOLVED (kept for the diagnosis method and the alerting gap),
and ks2/plan records that the interim push was deliberately not
re-enabled.

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

2026-08-31 09:32:29 +02:00

jellyfin-client.md

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

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

jellyfin-server.md

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

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

nuc-install.md

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

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

README.md

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

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

usb4t-dropouts.md

docs: follow the storage move from nuc/USB to nas/SATA

2026-08-31 09:32:29 +02:00

README.md

Homelab: nuc

Incus host on the LAN — on-demand: since 2026-08-30 it only needs to run when watching Jellyfin or using the Spotify Connect kiosk. Everything always-on (blocky/DNS, privoxy, transmission-bt) moved to nas, which is why nuc can now be powered off.

⚠️ Powering nuc off has backup consequences — its 03:30 replication to nas only runs while it is up. See nas-install.md §9.

Debian 13, Intel Alder Lake-N (iGPU i915, shared by both Jellyfin containers) — bare-metal reinstall: nuc-install.md
Instances are bridged onto the LAN (192.168.0.0/24)
Storage: ZFS pool data on the SSD (all instance disks). The USB 4 TB and its pool left nuc on 2026-08-30 — the enclosure's JMicron bridge was suspending the pool (usb4t-dropouts.md); the disk now sits on direct SATA in nas as pool tank.
Media library: /srv/media is now an NFSv4 mount from nas (192.168.0.4:/media, read-only). jellyfin-server stays here for the iGPU and reads it with shift=false (jellyfin-server.md).
Backups: nuc and nas cross-replicate — nuc pushes all its instances to nas:nucbackup at 03:30, nas pushes its own to nuc:nasbackup at 04:00, so neither host's instances depend on that host surviving (nas/nas-install.md §9). The ks4 pull leg moved to nas as well (ks2/nas-seed.md), so nuc no longer runs a WireGuard tunnel.
⚠️ Never reboot nuc with the display powered on — the i915 probe dies and takes every container with it (including LAN DNS). Symptoms and fix: jellyfin-client.md

Instances

Name	IP	Doc	Features
jellyfin-server	192.168.0.5	✅	unprivileged, autostart; iGPU render node (`gpu` device, render gid) for QSV/VAAPI transcoding; `/srv/media` disk device (NFS from nas, `shift=false`, read-only); proxy device → host :8096
jellyfin-client	192.168.0.6	✅	privileged, autostart; full iGPU (`gpu` device, gid 44) → HDMI kiosk (cage + Jellyfin Media Player); custom `raw.lxc` (bind `/dev/snd`, `/dev/input`, host `/run/udev`); Pioneer USB audio as ALSA default; FR keymap; go-librespot Spotify Connect ("Pioneer A-70")
homeassistant	(stopped)	—	virtual machine, 50 GiB root disk on pool `data`

Moved to nas on 2026-08-30: transmission-bt (next to the media dataset it writes to), plus blocky and privoxy so LAN DNS and the proxy survive nuc being shut down.