docs(audit): mark tsys6/tsys9 S1 storage.cfg fixes as resolved

Operator corrected the tsys6 S1 export path (S21 -> S1) and added the missing
S1 entry to tsys9. Verified both via pvesm status: all 8 NFS stores active on
each host. Updated audit findings table, §5.1/§5.2, and Phase 0 checklist.

💘 Generated with Crush

Assisted-by: Crush:glm-5.2

STATUS.md

@@ -40,8 +40,8 @@ infrastructure, Proxmox cluster ops, and k8s control plane.
 - [x] Capacity goals codified (80% RAM / ~50% idle CPU + workload model)
 - [x] **Storage topology corrected:** `local-nonprod` = S1 disk (not separate); per-host storage.cfg
 - [x] cnode5 (706) deleted; cnode4 (601) stopped (delete pending)
+- [x] **tsys6 S1 typo + tsys9 missing S1 — both FIXED by operator** (verified: 8/8 NFS stores active on both)
 - [ ] CPU ~50%-idle goal: fleet idles 0-5% (under-utilized; chase via workloads, not hardware)
-- [ ] **BUG: tsys6 S1 export path typo** (`S21` instead of `S1`) — S1 broken on tsys6
 - [ ] tsys4: blocked on PCIe NIC + RAM install
 - [ ] tsys5: blocked on 2nd ethernet cable + NVMe install; **also single-CPU** (CPU2 socket empty)
 - [ ] tsys2: pending rebuild from Win10 to Proxmox

proxmox/docs/AUDIT-2026-07-29.md

@@ -23,8 +23,8 @@ dumps + ~05:40 CDT capacity probe). Storage configs read directly from
 |---------|----------|---|
 | **D2 carries 17 VMs** — the worst IOPS hotspot in the fleet | High | 5 |
 | **S1 is NOT empty — it carries 16 sectestbed VMs via `local-nonprod`** (previous audit was wrong) | High | 4, 5 |
-| **tsys6 S1 NFS export is broken** (typo: path says `S21` not `S1`) | Bug | 6 |
-| **tsys9 has no S1 in storage.cfg** — can't target S1 from tsys9 | Config gap | 6 |
+| ~~tsys6 S1 NFS export typo~~ (`S21`) — **FIXED by operator 2026-07-29**; all 8 stores active | Resolved | 6 |
+| ~~tsys9 missing S1~~ in storage.cfg — **FIXED by operator 2026-07-29**; S1 active | Resolved | 6 |
 | **`local-nonprod` on tsys5 = the S1 physical disk** (dir storage, not a separate disk) | Topology | 4 |
 | **tsys5 is single-CPU** (CPU2 socket unpopulated; prior "dual E5620" was wrong) | Medium | 9 |
 | **cnode4 (601) stopped, cnode5 (706) deleted** (user action this session) | Resolved | 10 |
@@ -120,22 +120,16 @@ S1.** Target S2, S3, S4, and D5 for IOPS spreading.
 
 ## 5. Storage bugs and config gaps found
 
-### 5.1 BUG: tsys6 S1 export path typo (S21)
+### 5.1 BUG: tsys6 S1 export path typo (S21) — RESOLVED ✓
 
-On tsys6's `/etc/pve/storage.cfg`:
-```
-nfs: S1
-    export /mnt/pfv-tsys5/S21    ← should be S1, not S21
-```
+**Fixed by operator 2026-07-29.** The export path was corrected from `S21` to
+`S1`. Verified: `pvesm status` on tsys6 shows all 8 NFS stores active, including
+S1 (96 GB, 10.3% used by the sectestbed VMs visible via NFS).
 
-**S1 is broken on tsys6.** Any attempt to move a VM disk to S1 on tsys6 will
-fail. Fix: change `S21` → `S1`.
+### 5.2 GAP: tsys9 missing S1 in storage.cfg — RESOLVED ✓
 
-### 5.2 GAP: tsys9 has no S1 in storage.cfg
-
-tsys9 defines S2, S3, S4, T5-SSD but **not S1**. If any VM on tsys9 ever needs
-S1 storage, the entry must be added first. (Given that S1 is already loaded with
-16 sectestbed VMs, this is low priority — but the gap should be noted.)
+**Fixed by operator 2026-07-29.** S1 entry added to tsys9's storage.cfg.
+Verified: all 8 NFS stores active on tsys9, S1 listing identical to tsys6.
 
 ### 5.3 ORPHANED: D1 and D7 exports on tsys4
 
@@ -378,12 +372,10 @@ HA pairs stay split:
 
 ## 11. Action checklist (do in this order)
 
-### Phase 0 — fix storage config bugs first
+### Phase 0 — fix storage config bugs first — DONE ✓
 
-- **Fix tsys6 S1 typo:** edit `/etc/pve/storage.cfg` on tsys6, change
-  `export /mnt/pfv-tsys5/S21` → `export /mnt/pfv-tsys5/S1`
-- **(Optional) Add S1 to tsys9 storage.cfg** (low priority — S1 is already
-  loaded; only needed if a tsys9 VM ever targets S1)
+- ~~Fix tsys6 S1 typo~~ — **operator fixed 2026-07-29** (verified: 8/8 stores active)
+- ~~Add S1 to tsys9 storage.cfg~~ — **operator fixed 2026-07-29** (verified)
 
 ### Phase 1 — cleanup