skic-v1-playground/knowledge-wiki
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wiki: sync 2026-08-26 03:05 UTC — 10 file(s) updated

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-26 03:05:01 +00:00
parent 0ad2021ca2
commit 39ecb4cff5
10 changed files with 224 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
channels/1519072621130547220.md
+11 -1
View File
@@ -1,6 +1,6 @@
# Channel Wiki: #jarvis-jr-truenas
_Channel ID: 1519072621130547220_
_Last sync: 2026-08-19 03:03 UTC_
_Last sync: 2026-08-26 03:03 UTC_
## Purpose
TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discussions.
@@ -29,6 +29,16 @@ TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discuss
- Startup marked two interrupted cron executions `unknown` after restart. It also logged repeated operational friction: `hermes: command not found` in tool shells, `discord.server_actions` configured with unsupported action `all`, unavailable web-dependent tools because `check_web_api_key` returned false, Git commands launched outside a repository, and one command held for security approval.
- **CONFIRMED security warning:** the API server was bound to `0.0.0.0` while `terminal.backend` was `local`/unsandboxed, meaning trusted-network firewalling or a sandboxed terminal backend should be evaluated. This is an investigation finding only; RootAtSkic explicitly prohibited configuration changes at this stage.
## Live DIMM inventory — 2026-08-25 (read-only)
- Host SMBIOS Type 17 reports **96 GiB installed** as **2 × 48 GiB G.Skill DDR5 UDIMMs**, part `F5-5200J4040A48G`, dual-rank. The DIMMs advertise 4800 MT/s in SMBIOS and are configured at 4400 MT/s.
- The board manual identifies the physical channels/slots as `DDR5_A1`, `DDR5_A2`, `DDR5_B1`, and `DDR5_B2`; its priority-two-DIMM configuration is **`DDR5_A2` + `DDR5_B2`**. This matches RootAtSkic's recollection of one DIMM in channel A and one in channel B.
- Firmware exposes those two occupied records under Intel internal locator names `Controller0-ChannelA-DIMM1` and `Controller1-ChannelA-DIMM1`; these strings must not be presented as the motherboard's physical channel labels. Their SMBIOS/SPD serial identifiers are `FC5AF1F5` and `765377F8`. These eight-hex-digit IDs may differ from a longer serial/barcode printed on each DIMM label.
- **OPEN verification concern (RootAtSkic, 2026-08-25):** one reported eight-character identifier contains letters while the other contains only numerals. The fetched window contains no response resolving that concern. Treat both values only as unverified SMBIOS-reported hexadecimal identifiers—not confirmed physical-label serial numbers—until raw records/SPD or DIMM labels are independently checked. Source: Discord message `1541875756626354266`.
- SMBIOS does not expose module manufacturing week/year. Determining production date requires readable SPD EEPROM data or inspection of the physical DIMM labels; neither was available from the container during this check.
### Source anchor
- Latest processed human message: `1541875756626354266` (2026-08-25 18:23 UTC).
## TrueNAS Stability Incident — 2026-08-17
- TrueNAS `26.0.0-BETA.2` on `nas.lego-cloud.eu` underwent full-host boots at 11:02:52, 12:16:18, 12:32:13, and 13:52:25 Europe/Vilnius time. Docker/containerd restarts were consequences, not the initial cause.
- Recursive recovery of `/var/lib/systemd/pstore` proved that all observed Aug 17 outages followed explicit kernel panics. Fifteen panic records are persisted from Aug 4–17, all using kernel `6.18.23-production+truenas` and OpenZFS `2.4.1-1`.