diff --git a/README.md b/README.md index b0aef28e..0ea79cf1 100644 --- a/README.md +++ b/README.md @@ -357,8 +357,8 @@ what gates it, and why it is in that order. What happened, and what it found, is [`docs/changelog.md`](docs/changelog.md), dated and never rewritten. The current top items: rehearse the firewall restore on the ProDesk bought on -2026-09-08 — on hand since 2026-09-14, so what the rehearsal waits on is the -I226 card and the installer stick and no longer the box — and then build the +2026-09-08 — on hand since 2026-09-14, with its I226 card fitted since +2026-09-25, so what the rehearsal waits on is the installer stick alone — and then build the sensitive tier on that same box ([#404](https://github.com/Gerrrt/HomeLab/issues/404), [ADR-0034](docs/adr/0034-run-the-sensitive-tier-on-the-prodesk-and-make-it-the-spare-hardware.md)). **Every purchase still outstanding is in one place**, the roadmap's [*Everything still to buy*](docs/roadmap.md#everything-still-to-buy): one item now, one later, and a rule that nothing joins them without a diff --git a/docs/changelog.md b/docs/changelog.md index 3a32c4d1..923d28ae 100644 --- a/docs/changelog.md +++ b/docs/changelog.md @@ -17,6 +17,19 @@ roadmap as it read that day, and the *Done* entries keep the shape they had there. `check_docs.py` does not check this file, for the reason its module docstring gives: it is a record, not a claim about now. +## 2026-09-25 + +- **The I226 card arrived and is fitted in `trinity`.** It went into the + second M.2 slot, which was found free on 2026-09-15, so the fit question + in `hardware.md` is answered. That leaves the installer stick as the only + thing [#92](https://github.com/Gerrrt/HomeLab/issues/92)'s rehearsal + waits on. The card's part number and MAC are still unread. Whether the + card comes up as `igc0` is for the rehearsal to show. +- **`smaug`'s memory has not shipped.** Memory.NET held the 2026-09-22 + order for an identity check. It was answered today, so `hardware.md` no + longer says the modules are in transit + ([#599](https://github.com/Gerrrt/HomeLab/issues/599)). + ## 2026-09-23 - **[#485](https://github.com/Gerrrt/HomeLab/issues/485): the build runbook diff --git a/docs/hardware.md b/docs/hardware.md index b7cf09e8..504bbd6e 100644 --- a/docs/hardware.md +++ b/docs/hardware.md @@ -146,13 +146,13 @@ revisions of this repository treated `shiva` as the hypervisor itself. [#404](https://github.com/Gerrrt/HomeLab/issues/404) builds it, after the firewall restore has been rehearsed on it. It ships with the onboard NIC only; the I226 card the restore depends on was a separate purchase, made - 2026-09-11 and the entry below — which has **not** landed. So what the - rehearsal waits on is no longer this box: it is that card and the installer - stick. **The 512 GB SSD is M.2, and the second M.2 slot is free** — read off - the machine on 2026-09-15, and the answer the entry below was waiting for. - There is no drive carrier and nothing contends: the I226 card has a slot to - land in when it arrives, and the contingency the documents carried since - 2026-09-11 does not fire. + 2026-09-11 and the entry below — **in hand and fitted since 2026-09-25**. + So what the rehearsal waits on is no longer this box or the card: it is the + installer stick alone. **The 512 GB SSD is M.2, and the second M.2 slot is + free** — read off the machine on 2026-09-15, and the answer the entry below + was waiting for. There is no drive carrier and nothing contended: the I226 + card went into that slot on 2026-09-25, and the contingency the documents + carried since 2026-09-11 did not fire. **It arrived carrying Windows 11 Pro**, sold refurbished with a licence. The rehearsal's first act is to wipe it, so that licence is spent rather than banked: it is OEM, it dies with the install it shipped on, and **it does not @@ -176,9 +176,10 @@ revisions of this repository treated `shiva` as the hypervisor itself. **read them before that date**. Installing pfSense over the Windows partition is what ends the return and is the one step of the rehearsal that cannot be taken back, so the machine has to be proved while sending it back is still an - option. That is sooner than the card arrives, and it does not wait on it. + option. It waits on nothing. - Intel I226-V 2.5 GbE card on an M.2 B+M-key adapter — bought 2026-09-11, - in transit. The second port on the ProDesk Micro above, matching the card + **in hand since 2026-09-25 and fitted in `trinity` the same day**. The + second port on the ProDesk Micro above, matching the card in `morpheus` so a pfSense restore onto the spare brings the LAN up as `igc0` and asks nothing ([`restore-the-firewall.md`](runbooks/restore-the-firewall.md), @@ -193,10 +194,12 @@ revisions of this repository treated `shiva` as the hypervisor itself. want the same space, and that one of them would have to go. It was a real risk and it did not happen; recorded as answered rather than deleted, because the reason the card was bought before the box was opened is the - part worth remembering. Part number and the port's MAC go here when it - lands, as does confirmation that the free slot takes a B+M-key 2280 card — + part worth remembering. **The free slot took it**, fitted on 2026-09-25 — `morpheus` is the same model and does exactly this, which is why the same - model was bought. + model was bought. Still to read: the part number off the card, and the + port's MAC. The Windows the box shipped with shows the MAC before the + rehearsal wipes it; after the install, FreeBSD shows it on `igc0`, which is + also the proof that the driver claimed the card. - 2 TB USB portable hard drive — on hand, previously a games console's storage. Becomes the photo library's disk on `trinity` ([#404](https://github.com/Gerrrt/HomeLab/issues/404)): Immich's originals @@ -729,8 +732,10 @@ revisions of this repository treated `shiva` as the hypervisor itself. procedure and a section on what differs on this host. Nothing in the Compute table changes; a cell is not a spec. - Three Samsung `M391A1G43EB1-CPB`[^Smaugmem] — 8 GB DDR4-2133 ECC UDIMM, - PC4-17000P-E, dual rank x8 — **bought 2026-09-22, in transit**, under - [#599](https://github.com/Gerrrt/HomeLab/issues/599). `smaug`'s memory, and + PC4-17000P-E, dual rank x8 — **bought 2026-09-22** under + [#599](https://github.com/Gerrrt/HomeLab/issues/599), **not yet shipped**: + the seller held the order for an identity check, answered 2026-09-25. + `smaug`'s memory, and the same part as the module the machine already carries: this is the matched-set answer to that issue rather than the two-16 GB one, for the reason the Compute entry above now records. $44 each, $132 the three, $15.30 diff --git a/docs/roadmap.md b/docs/roadmap.md index 53261a8d..0a0ae313 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -110,7 +110,8 @@ has been rehearsed on it. restore.** First, because the box was sold with a thirty-day return that closes **2026-10-08**, and installing pfSense over the Windows it arrived with is both the step that proves the machine and the step that ends the - return. Gate: the I226 card and the installer stick. The rehearsal is what + return. Gate: the installer stick; the I226 card was fitted on 2026-09-25. + The rehearsal is what turns the runbook from a hypothesis into a procedure. → [runbook](runbooks/restore-the-firewall.md) - **[#404](https://github.com/Gerrrt/HomeLab/issues/404) Build the tier's diff --git a/docs/runbooks/restore-the-firewall.md b/docs/runbooks/restore-the-firewall.md index 2586c4ac..6e8975cf 100644 --- a/docs/runbooks/restore-the-firewall.md +++ b/docs/runbooks/restore-the-firewall.md @@ -364,10 +364,11 @@ becomes a list of what is blocking: back. So prove the machine — spec, serial, NIC count, disk health — before that date. This is the only entry on this list with a deadline, and it is not waiting on the two entries below that are. -- **The I226 card** — bought 2026-09-11, **still in transit** - ([`hardware.md`](../hardware.md)). One of the two things the rehearsal now - waits on. -- **An installer for 2.9.0 or newer** — §3 step 1, and the other. The stick +- **The I226 card** — bought 2026-09-11, **in hand and fitted in the spare + since 2026-09-25** ([`hardware.md`](../hardware.md)). Whether it comes up as + `igc0` is a question for the rehearsal, below. +- **An installer for 2.9.0 or newer** — §3 step 1, and now the one thing the + rehearsal waits on. The stick in transit is whatever version it is; read it before the day. - **The newest export on `oracle`**, and the age key's offline copy. - **The numbers to check against**: `make backup-firewall ARGS=--verify-only`