All runbooks
evidenceuai-explorerredacted view

Lab Node Identity Survey Evidence

Synced UAI Explorer evidence documentation from docs/evidence/lab-node-identity-survey-2026-06-20.md.

Updated 2026-06-21·Freshness: Reference·Sensitive tokens or credentials were hidden before display.

Lab Node Identity Survey Evidence

Date: 2026-06-20
Timezone: America/St_Johns

Scope

Ran read-only identity checks against visible lab hosts to reduce the dormant future Proxmox-node blocker. This did not mutate production CT 121, sandbox CT 126, DNS, TLS, firewall, routes, Proxmox cluster membership, storage, snapshots, containers, VMs, or device filesystems.

Proxmox Cluster Identity

Observed pvesh get /cluster/status from the HomeLab cluster:

Node Address Online Interpretation
Director 10.0.0.250 yes Current Proxmox host used for UAI Explorer CT 121 and sandbox CT 126.
echo 10.0.0.249 yes Online Proxmox cluster node.
forge 10.0.0.248 yes Online Proxmox cluster node hosting CTs 103, 105, and 108.

The current visible HomeLab cluster has three online nodes. This evidence does not identify a fourth dormant/future node.

Host Classification

Address Hostname Read-Only Signal Classification
10.0.0.103 engineering Ubuntu 24.04 LTS, systemd-detect-virt=lxc, no pveversion. LXC guest on forge; lab jump host, not bare-metal dormant node.
10.0.0.105 wow-weekend Ubuntu 24.04 LTS, systemd-detect-virt=lxc, no pveversion. LXC guest on forge; not classified as UAI Explorer survey target.
10.0.0.108 satisfactory Ubuntu 24.04.4 LTS, systemd-detect-virt=lxc, no pveversion. LXC guest on forge; not classified as UAI Explorer survey target.
10.0.0.248 forge Debian 13, virt=none, pve-manager/9.0.3. Online Proxmox cluster node.
10.0.0.249 echo Debian 13, virt=none, pve-manager/9.0.3. Online Proxmox cluster node.
10.0.0.250 Director Debian 13, virt=none, pve-manager/9.1.4. Online Proxmox cluster node and current UAI Explorer host.
10.0.0.253 pihole CT 253 on Director, Debian 12, IP 10.0.0.253. Direct root BatchMode was denied. Infrastructure container, not dormant bare-metal node.
10.0.0.107 last known zenbook-14 Current checks show no local ARP entry, failed neighbor state from engineering and Director, 100% ICMP loss, and no TCP/22 route. Historical reachability note only; Zenbook is closed for UAI Explorer survey scope.

Container And VM Readout

forge:

  • CT 103: engineering, running.
  • CT 105: wow-weekend, running.
  • CT 108: satisfactory, running.
  • No QEMU VMs were listed.

echo:

  • No CTs or QEMU VMs were listed by the read-only checks.

Director:

  • CTs listed: 104, 115, 116, 117, 121, 123, 124, 125, 126, and 253.
  • No QEMU VMs were listed.
  • CT 253 reported hostname pihole.

Storage Signals

forge:

  • local: 46.25% used.
  • local-lvm: 63.10% used.

echo:

  • local: 83.92% used.
  • local-lvm: 0.00% used.

Director storage details remain recorded in [REDACTED:high-entropy].md.

Result

The dormant future Proxmox-node blocker is narrowed but not cleared:

  • The online HomeLab cluster nodes are now identified as Director, echo, and forge.
  • The visible guests and infrastructure service are classified.
  • No authoritative hostname or IP for the separate dormant/future node was found.
  • The dormant/future node still needs operator confirmation while powered on, followed by a metadata-only documentation survey before cluster join, disk reuse, or cleanup.