wiki: sync 2026-09-01 03:04 UTC — 6 file(s) updated
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Channel Wiki: #jarvis-jr-truenas
|
||||
_Channel ID: 1519072621130547220_
|
||||
_Last sync: 2026-08-29 03:03 UTC_
|
||||
_Last sync: 2026-09-01 03:03 UTC_
|
||||
|
||||
## Purpose
|
||||
TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discussions.
|
||||
@@ -29,6 +29,7 @@ TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discuss
|
||||
## Active Topics
|
||||
- TrueNAS application deployment patterns.
|
||||
- Harbor/container-registry architecture and certificate/routing requirements.
|
||||
- **OPEN Discord visibility/response incident (2026-08-31):** New member Giedrius K asked “where are other channels?” while mentioning Hermes, but the message did not trigger an agent turn. RootAtSkic then asked why Hermes was ignoring him. Hermes said the message appeared only later as recent context, not as a triggering message, and committed to inspect Discord channel visibility/permissions rather than guess. The exact trigger failure, which channels Giedrius expected, the relevant permission state, owner, and due date are **UNKNOWN**. Next action: inspect the guild/channel visibility and Hermes trigger path, then answer Giedrius. Sources: Discord messages `1543954078315454464`, `1543961473745944586`, and bot clarification `1543961597909672140`.
|
||||
- **PROPOSED dataset operation (RootAtSkic, 2026-08-28):** RootAtSkic asked whether Hermes can create a TrueNAS dataset. Hermes confirmed that `home-v1--truenas` supports authenticated dataset creation plus fresh readback, but no concrete creation request was supplied and **no dataset was created**. Before any write, obtain the exact dataset path/name, purpose, and any quota, encryption, compression, ACL, or permission requirements; inspect the target pool, limit the write to that specification, and verify it with a fresh API readback. Owner/requester: RootAtSkic. Due date: **UNKNOWN**. Next action: await the missing dataset specification and explicit request to create it.
|
||||
- **CONFIRMED capacity objective (RootAtSkic, 2026-08-17):** maximize this TrueNAS host's memory. For the documented W680D4U-2L2T/G5 / i9-14900KS platform, the target is `192 GB ECC` (`4 × 48 GB DDR5 ECC UDIMM`), not a smaller diagnostic kit. Procurement and validation constraints are recorded below.
|
||||
- **OPEN investigation request (RootAtSkic, 2026-08-18):** review the attached Hermes container startup log and identify improvements, but **do not change anything yet**. No response or approved implementation was present in the fetched history; RootAtSkic followed up twice asking whether Hermes was alive. Source attachment: Discord message `1539151473189978142`, `message.txt`.
|
||||
@@ -47,7 +48,7 @@ TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discuss
|
||||
- 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: `1542993044880629810` (2026-08-28 20:23 UTC). RootAtSkic asked which skill is used for TrueNAS; the confirmed answer remains the dedicated `home-v1--truenas` skill and its private Gitea repository recorded above.
|
||||
- Latest processed human message: `1543961473745944586` (2026-08-31 12:31 UTC). RootAtSkic asked why Hermes had not answered Giedrius K's channel-visibility question; the open incident and next action are recorded above.
|
||||
|
||||
## 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.
|
||||
|
||||
Reference in New Issue
Block a user