All runbooks
evidenceuai-explorerredacted view

Proxmox Storage Review Evidence

Synced UAI Explorer evidence documentation from docs/evidence/proxmox-storage-review-2026-06-20.md.

Updated 2026-06-21·Freshness: Reference·No secret-like patterns were observed in this view.

Proxmox Storage Review Evidence

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

Supersession note: this is historical read-only storage evidence. It did not authorize cleanup. The 2026-06-21 production cutover used backup-only authority and no snapshot deletion or pruning.

Scope

Ran read-only Proxmox storage, LVM, snapshot, container, and VM inventory checks across the visible HomeLab Proxmox nodes: Director, echo, and forge.

This did not mutate production CT 121, sandbox CT 126, DNS, TLS, firewall, routes, Proxmox cluster membership, storage allocation, snapshots, containers, VMs, or device filesystems.

Cluster-Wide Summary

Node Address Proxmox Root Filesystem Local Storage Local-LVM VG Free Snapshot Signal
Director 10.0.0.250 pve-manager/9.1.4 18% used, 74 GiB available 16.97% used 28.87% used 16.00 GiB 7 CT snapshot LVs observed.
forge 10.0.0.248 pve-manager/9.0.3 49% used, 46 GiB available 46.25% used 63.10% used 16.00 GiB No CT snapshots listed; CT 103 large disk is 98.46% used.
echo 10.0.0.249 pve-manager/9.0.3 89% used, 11 GiB available 83.92% used 0.00% used 0.00 GiB No CTs, no VMs listed; local root storage is tight.

No QEMU VMs were listed on Director, echo, or forge.

Director Snapshot Inventory

Director hosts the UAI Explorer production and sandbox containers. Its thin pool is not close to full by data or metadata percentage, but VG free space is limited and snapshot lineage exists.

Observed snapshot LVs:

CT Snapshot Note
115 pre-archive-2026-04-20 Archived aux; description says preserve disk/config and do not reuse without review.
116 pre-archive-2026-04-20 Archived hedge; description says preserve disk/config and do not reuse without review.
117 pre-archive-2026-04-20 Archived hedge-firm; description says preserve disk/config and do not reuse without review.
126 migration-ready-20260620-081634 UAI Explorer 0.2.1 rollback rehearsal baseline.
126 mr022-20260620-190655 UAI Explorer 0.2.2 rollback rehearsal baseline.
126 mr022g-20260620-191542 UAI Explorer 0.2.2 readiness with raw survey mount guard.
253 pre-gpu-move Pi-hole snapshot before GPU move from forge to echo.

High-use CT disk noted:

  • CT 124 (cortex-sandbox-vnext) root disk is 16 GiB with 81.30% thin data usage.

Forge Storage Notes

forge hosts CTs 103, 105, and 108.

CT Hostname Disk Signal
103 engineering Rootfs is 170G; thin data usage was 98.46%. It also has host mounts /mnt/skip_data and /mnt/toshiba.
105 wow-weekend Rootfs is 120G; thin data usage was 25.07%.
108 satisfactory Rootfs is 80G; thin data usage was 14.21%.

forge local-lvm is 63.10% used. This is not an immediate full-pool condition, but CT 103 should be treated as a targeted cleanup/review candidate before adding more storage-heavy workloads.

Echo Storage Notes

echo had no CTs and no QEMU VMs listed by the read-only checks. Its local-lvm thin pool showed 0.00% used, but VG free space showed 0.00 GiB and the root filesystem was 89% used with 11 GiB available. /var/lib/vz/template used about 7.4 GiB.

This makes echo a host maintenance candidate before assuming it has easy headroom for staging, backups, templates, or incoming workloads.

Interpretation

The prior vague storage warning is now a specific maintenance decision:

  • Do not create more rollback snapshots for UAI Explorer until an operator decides which existing snapshots must remain.
  • Do not delete snapshots from UAI Explorer automation; the archived CT descriptions explicitly say to preserve and review.
  • Before snapshot-heavy work, review CT 126 snapshot retention, archived CTs 115/116/117, CT 253 pre-gpu-move, forge CT 103, and echo root/local template usage.
  • Production CT 121 remains untouched and does not currently have snapshots listed in this evidence pass.

Result

The storage blocker is narrowed but not cleared. Read-only review is complete; operator-approved maintenance policy is still required before cleanup, snapshot deletion, backup pruning, workload migration, or snapshot-heavy UAI Explorer work.