docs(pfi-gx10,nh3-pve): AC-restore patch validated; nh3-pve OOB held blind until next NH3 visit (NanoKVM → gx10, MS-01 → own vPro)

This commit is contained in:
vh
2026-09-25 13:34:17 -07:00
parent 2bf418c510
commit 2b49be4972
4 changed files with 35 additions and 16 deletions
+9 -5
View File
@@ -54,7 +54,7 @@ trivially while the desktop is still running.
The playbook will not stop GDM while someone holds a seat session. Override with
`--var force_dm_stop=true`, or just let the rack-install reboot handle it.
## Power-on after AC loss — patched, NOT YET VALIDATED (2026-09-24)
## Power-on after AC loss — patched 2026-09-24, VALIDATED 2026-09-25
There is **no BMC**, and the ASUS firmware ships with "Restore AC Power Loss" set
to stay off, so the box did not come back after the 2026-09-24 NH3 power outage.
@@ -80,10 +80,14 @@ are not on this board, and trusting that claim cost two trips to the power butto
(infra-ops, 1421 and 1435 on 2026-09-24). **The only valid test is pulling and
restoring AC power without touching the button.**
**Status at end of 2026-09-24:** the box is OFF (the 1435 shutdown), with the patch
in place. Prime will pull and restore AC on 2026-09-25. It comes up on its own →
the patch works, so delete "NOT YET VALIDATED" above. It stays off → press the
button, then revert with the backup and set it in the firmware menu via a PiKVM.
**Validated 2026-09-25 (Prime, relayed by Miranda):** the box had been off since
the 09-24 1435 shutdown. Prime pulled and replugged AC, and it **came up by itself**,
booting at 1108:54 PT without the button being pressed. The patch works; keep the
backup, since a firmware update may reset `Setup`. Re-check after any BIOS update
the same way, by pulling AC and not by a shutdown.
**Planned OOB (Prime, 2026-09-25):** nh3-pve's NanoKVM moves here on the next NH3
site visit. That also gives this box its first console. See `servers/nh3-pve/README.md`.
## Training — run 3c is staged and ready