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
Proxmox VE hypervisor for the ESH home lab (pve.esteban.net). Non-PFI scope.
Network
- LAN IP: 10.0.250.35
- FQDN:
pve.esteban.net - Web UI:
https://10.0.250.35:8006 - SSH:
root@esh-pve(key auth)
Hardware
- CPU: 13th Gen Intel Core i9-13900H
- RAM: 62.5 GB
- Kernel:
6.8.12-16-pve(Proxmox 8.x) - Storage: local
pve-rootat 94G (21% used) + two large NFS mounts from10.0.50.50:/mnt/pve/esh-nas— 92 TB available on/mnt/pvestore/mnt/pve/tank-vmbu— 93 TB, VM backup target (~1.4 TB used)
What it runs
esh-docker-vm (10.0.50.45) is a VM here. Other home-lab VMs are not yet catalogued in this workspace — run qm list on the host for the live inventory.
Refresh state
scripts/refresh-server-info.sh esh-pve
Same Proxmox-inspect caveat as pfi-pve.
Placement rule
Hypervisor for ESH home-lab VMs. Not part of the PFI colo topology.