admin/felhom.eu
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs: R-58 assisted disk-picker install mode + HP mini ISO profile notes

Browse Source 
R-58 records the operator ruling (2026-07-21) with the argument verbatim: the
installer should list available storage devices, excluding the install media,
and let one be selected. Third ISO mode alongside unattended-serial and
match-nothing-safety; unattended stays the appliance/factory mode. Slice 1 is
the abort-screen candidate table, same enumeration code, and it collapses the
two-boot dance on its own. Matters most for BYO/reinstall, where the serial is
unknown and a wrong guess is destructive.

ISO README gains the HP section: shim proven on this board by the safety boot,
the uncommitted-armed-profile pattern, verify-from-inside-the-ISO, and a
pointer to the prior-LVM abort that is the one likely failure on a
second-hand disk.
This commit is contained in:
authentik Default Admin
2026-07-21 18:00:21 +02:00
parent 0073691231
commit 2143ae2d8d
2 changed files with 32 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/iso/README.md
+31
View File
@@ -138,6 +138,37 @@ disables itself, and scrubs the env. Retry-vs-resume: the first attempt is plain
that finds `/var/lib/felhom-install/state.json` adds `--resume` (safe per host-install v1.11.3 — its
producer steps re-run each pass).
## HP mini profile (second pilot board, 2026-07-21)
`profiles/hp.profile` — same shape as the N100 template with ONE deliberate difference: **the loader
default stays at the stock signed `shim`**, so Secure Boot keeps working. `mkimage` exists only to
work around the N100's AMI firmware GRUB defect and is unsigned.
**PROVEN on this board (safety boot, operator-photographed 2026-07-21):** the shim loader booted, the
answer file was fetched and parsed, and the match-nothing filter refused with **zero disk writes** —
so the loader, Secure Boot setting, and network/answer path are all confirmed before anything
destructive existed on a stick. `enp1s0f0` auto-detect verified on-board.
**Arming it:** never edit the committed profile. Copy it to an UNCOMMITTED working profile (the
`n100-demo.profile` precedent — a real serial never goes in git), replace the placeholder serial, and
rebuild. Verify the armed filter by extracting `answer.toml` **from inside the built ISO**, and again
from the written stick — the profile is what you intended, the ISO is what you shipped:
```
osirrox -indev <iso> -extract /answer.toml /tmp/a.toml && sed -n '/^\[disk-setup\]/,$p' /tmp/a.toml
```
**Confirm the serial is the system disk and not a data drive.** On this board the SanDisk X600 128GB
(`sda`) is the system disk; the 1TB NVMe is the future data drive and must stay OUTSIDE the filter —
it joins later through the normal Tárhely flow, not the installer.
> **The one known failure mode on a second-hand board — read step 3 below.** The auto-installer does
> NOT force-clear a pre-existing LVM PV signature. A disk carrying a previous Linux/Proxmox install
> aborts at *"cannot init physical volume"* (spike S2b). A previous Windows/NTFS install is fine. If
> the install aborts that way, wipe the target first (`blkdiscard -f /dev/<disk>`, or `wipefs -a` plus
> zeroing the PV region) from any live environment, then re-boot the same stick — the ISO does not
> need rebuilding.
## N100 profile (for RUNBOOK B)
Use the committed `profiles/n100.profile` template (cheap-board, `FELHOM_LOADER="mkimage"`). **A real