All runbooks
evidenceuapiredacted view

UAPI Forge SN850X Read-Only Evidence 2026-06-22

Read-only Forge evidence confirming SN850X is mounted at /mnt/skip_data with high free capacity, pending storage policy gate.

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

UAPI Forge SN850X Read-Only Evidence 2026-06-22

Read-only Forge evidence confirming SN850X is mounted at /mnt/skip_data with high free capacity, pending storage policy gate.

Promotion Metadata

  • Source feedback id: 139
  • Source feedback ids: 139
  • Promotion request id: 70
  • Feedback category: beneficial
  • Feedback source: [REDACTED:high-entropy]
  • Feedback created at: 2026-06-22T19:43:53.396116+00:00
  • Target slug: [REDACTED:high-entropy]
  • Review state: review
  • Reviewer note: AI lane auto-promoted redacted feedback into internal catalog context.

Source Feedback Body

Feedback 139

  • Product: uapi
  • Category: beneficial
  • Related slug: [REDACTED:high-entropy]
  • Source: [REDACTED:high-entropy]
  • Created at: 2026-06-22T19:43:53.396116+00:00

Forge SN850X Read-Only Evidence (2026-06-22)

Authority: Codex acting-operator read-only inventory. No writes, mounts, formats, installs, model work, route changes, storage allocation changes, or destructive actions were performed.

Supersession Note

This updates the earlier SN850X re-inventory result. SN850X was not found on NUC-IPEX, the VPS/Cortex host, or Director, but the operator clarified that it is on Forge. A direct read-only Forge check confirmed that.

Forge Target

  • Host: forge
  • Address checked: 10.0.0.248
  • Platform: Proxmox pve-manager/9.0.3
  • Access: SSH read-only command pass

SN850X Finding

Forge has a WD_BLACK SN850X HS 1000GB NVMe device visible as nvme1n1.

Observed layout:

  • nvme1n1: about 931.5G disk, model WD_BLACK SN850X HS 1000GB
  • nvme1n1p1: about 1G, vfat, not mounted
  • nvme1n1p2: about 930.5G, ext4, mounted at /mnt/skip_data

Filesystem view:

  • Mount: /mnt/skip_data
  • Source: /dev/nvme1n1p2
  • Type: ext4
  • Size: about 915G
  • Used: about 94G
  • Available: about 775G
  • Use: about 11%

Other visible Forge storage:

  • sda1: ext4 mounted at /mnt/toshiba, about 916G size, about 847G available
  • Proxmox boot/LVM NVMe: WDC WDS500G2B0C-00PXH0, about 465.8G, used for Proxmox root/LVM
  • local-lvm: active, about 63.11% used
  • CTs visible: 103 engineering, 105 wow-weekend, 108 satisfactory
  • CT 103 disk signal remains tight: vm-103-disk-1 about 170G with about 98.46% data use

Interpretation

SN850X is present and mounted, but it should not be treated as automatically free infrastructure capacity. Current evidence supports:

  • forge.storage.sn850x.skip_data: present, ext4, mounted at /mnt/skip_data, high free space
  • storage.fast.sn850x: candidate route only, pending ownership and adapter policy
  • lab.proxmox.forge: confirmed host for the SN850X

The SN850X is not currently shown as Proxmox pvesm storage in this readout. It is a host-mounted ext4 filesystem, so UAPI use would need a deliberate storage adapter/export policy rather than assuming Proxmox LVM or VM disk availability.

Safe Next Step

Do not move workloads or model caches yet. Next safe work is an explicit storage policy/adapter design:

  1. Decide whether /mnt/skip_data is allowed to serve UAPI artifacts, model cache, embedding cache, or only manual scratch.
  2. Define ownership, allowed paths, quotas, cleanup policy, and audit logging.
  3. Run a read-only directory/top-level usage inventory if approved.
  4. Only after policy approval, design a UAPI storage adapter route.

Blockers

  • Ownership/policy for /mnt/skip_data not confirmed.
  • No write or allocation approval.
  • No UAPI storage adapter exists for this mount.
  • CT 103 disk pressure is separate and should not be solved by ad hoc writes to SN850X without a policy.