vh
2118449881
nh3-pve and esh-pve are the same Minisforum MS-01 (BIOS AHWSA.1.17). With a card in the x16 slot its root port takes bus 01 and every NIC moves down a bus (measured on esh-pve), so predictable names change (enp2s0f0np0 -> enp3s0f0np0 etc.) and vmbr0 would boot with no uplink. systemd .link files now pin all NICs by MAC, baked into every initramfs and synced to the ESP; udev confirms the files apply. The AMT-capable I226-LM (enp88s0) leaves vmbr0's bridge-ports in the file (next boot), so cabling it for AMT cannot loop the STP-less bridge. Also: documented the NanoKVM (https://10.100.250.171) as nh3-pve's console OOB and that AMT is not wired; nh3-dev's Beszel agent no longer binds NAS shares (it died on the last NH3 cold start); post-boot checklist in persistent-memory.
12 lines
662 B
YAML
12 lines
662 B
YAML
# nh3-dev — deliberately NO extra filesystems (changed 2026-09-25).
|
|
#
|
|
# This override used to bind /mnt/backup and /mnt/smithy, two nh3-nas NFS
|
|
# shares. Since 1cbde50 those are automounted on first access, and on an NH3 cold
|
|
# start the NAS is the slowest box up. Docker then failed to bind the share
|
|
# ("no such device"), and it never retries a container that fails to CREATE, so
|
|
# the agent stayed dead from the 2026-09-24 power recovery until it was noticed.
|
|
# Their capacity is nh3-nas's own volume, which nh3-nas's agent already reports,
|
|
# so dropping them loses no information and removes the agent's dependency on the NAS.
|
|
services:
|
|
beszel-agent: {}
|