Repository navigation
docs(hardware): trinity's SSD is M.2 and the second slot is free (#404) - #474
Merged
Merged
Conversation
Opened on 2026-09-15. The 512 GB SSD is an M.2 stick, not a 2.5" drive in a carrier, and the second M.2 slot is free — so the I226 card has somewhere to land when it arrives and nothing contends for the space. That contingency had been carried in three places since 2026-09-11: the card's own entry in hardware.md, the ProDesk entry above it, and the rehearsal prerequisite list in restore-the-firewall.md. All three now record the answer. It is written as answered rather than deleted, because the reason the card was bought before anyone had opened the box is the part worth keeping — the same model as morpheus was chosen precisely so the slot would be there, and that reasoning held. What this does not do is confirm the machine. The i5-8500T, the 32 GB, the 512 GB and the onboard-NIC-only claim are all still the listing talking rather than the box, and the serial and product number have not been read off the case. Those stay recorded as owed. The one further check the card entry now names is that the free slot takes a B+M-key 2280 card, which morpheus demonstrates on the same model but which nobody has confirmed on this one. The rehearsal's blocking list goes from three items to two: the card and the pfSense installer stick, neither of which has landed. The box has left it. Refs #404 #92 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
trinitywas opened on 2026-09-15. Its 512 GB SSD is M.2, and the secondM.2 slot is free.
So the I226 card has somewhere to land when it arrives, and the drive-carrier
contention the documents have warned about since 2026-09-11 does not happen.
Nothing needs returning.
Where that contingency lived
Three places, all now recording the answer:
docs/hardware.mddocs/runbooks/restore-the-firewall.mdIt is written as answered rather than deleted. The reason the card was
bought before anyone had opened the box is worth keeping: the same model as
morpheuswas chosen precisely so that slot would be there, and the reasoningheld.
What this does not confirm
The i5-8500T, the 32 GB, the 512 GB and the onboard-NIC-only claim are still
the listing talking rather than the machine, and the serial and product number
have not been read off the case. All of that stays recorded as owed.
One further check is now named on the card's entry: that the free slot takes a
B+M-key 2280 card.
morpheusdoes exactly this on the same model, which iswhy the same model was bought — but nobody has confirmed it on this one.
Net effect
The rehearsal's blocking list goes from three items to two — the I226 card and
the pfSense installer stick, neither landed. The box has left it.
make validatepasses;check_docsgreen at 10 assertions.Refs #404 #92
🤖 Generated with Claude Code