vh
1431768596
Parallel to refresh-server-info.sh but pipes proxmox_inspect.sh and writes to servers/<host>/proxmox-details.txt. Same discovery / ssh-target / validate-only / dry-run behavior. Fleet-wide `all` matches dir names containing `-pve` (covers *-pve and *-pve-* so esh-pve-nas is included alongside pfi-pve / nh3-pve / esh-pve). Explicit names are never filtered — useful for one-off PVE hosts with non-matching names. Validation checks the captured snapshot for: truncation, missing PVE version line, non-Proxmox target, and surfaces backup-coverage "NO" verdict counts so gaps show up in the validate-only output. Initial fleet snapshot refreshed.
esh-pve-nas
Second Proxmox VE host at the ESH home lab (esh-nas-pve.esteban.net), dedicated to NAS / storage duty.
Network
- LAN IP: 10.0.50.55
- FQDN:
esh-nas-pve.esteban.net - Web UI:
https://10.0.50.55:8006 - SSH:
root@esh-pve-nas(key auth)
Media services on this box sit at 10.0.50.56 (Plex) and 10.0.50.57 (Jellyfin) — references to esh-nas-pve in the homepage config point at those addresses.
Hardware
- CPU: Intel Xeon W-1250 @ 3.30 GHz
- RAM: 125.6 GB
- Kernel:
6.8.12-13-pve(Proxmox 8.x) - Storage: local
pve-rootis tiny (5.9 GB, 87% used — worth watching) + NFS/mnt/pve/tank-vmbu(93 TB) for VM backups
Root-fs pressure: at 87% used on a 5.9 GB root partition, there's not much room for package upgrades or logs. Worth cleaning up or growing the root if this host is staying in production for a while.
What it runs
Media + storage-adjacent workloads for the ESH site. Not yet catalogued here; qm list / pct list on the host is authoritative.
The ESH-FileBot entry in homepage (10.0.50.70, labeled "Restic Backup Target and File Sync — esh-nas-pve") is a workload running here — mentioned in the backup project as a possible additional restic endpoint; confirm role before integrating into the fleet plan.
Refresh state
scripts/refresh-server-info.sh esh-pve-nas
Placement rule
Hypervisor for ESH storage/media VMs. Non-PFI scope.