ADR 0256: one module reads a machine's hardware condition, and a fault is said through its health #206

Merged

mesh-admin merged 4 commits from decision/hardware-sensors into main 2026-10-08 13:20:58 +00:00

Conversation 1 Commits 4 Files Changed 2

+267 -1

4 Commits

Author	SHA1	Message	Date
jochen	df41dfff38	ADR 0256: say exactly how a SAS drive, a USB drive and a stuck read are treated ... The SAS sentence now holds for modes with spaces, a hung read is unhealthy in two to three minutes, not one, every USB drive is told sat, and the limits of a stuck read are recorded.	2026-10-08 15:04:03 +02:00
jochen	0406373545	ADR 0256: one reader of the drives, and a stuck read is said ... After the second review: smartd is dropped as a second reader that could wake or keep awake the drives, a stuck read or a drive not looked at is unhealthy, a drive asleep for a day is HIGH and never unhealthy, and a board chip's maximum says nothing of a fan. The never-woken and hourly claims now say exactly what holds.	2026-10-08 14:59:12 +02:00
jochen	f63828ce1c	ADR 0256: say exactly what raises a condition, and why a drive is read only hourly ... Rule 4 now matches the module after review: the NVMe temperature bit, old-age attributes, a fan's minimum or alarm and a board chip's limits raise nothing; a stale watch does. The standby caveat is recorded: no mesh tool sees a drive's spin-down timer, so spinning drives are read hourly.	2026-10-08 14:35:21 +02:00
jochen	c8b6a4eea8	ADR 0256: one module reads the machine's hardware, so a failing drive or fan is raised, not found dead ... A machine's temperatures, fans and drive health were read by the laptop's vendor module only; the machines' 20 drives were watched by nothing. The sensors module reads them on every machine, holds no seat until a caller must reach it by role, and says a hardware fault through ADR 0240's health until the machine judges its own hardware. To-be 48 gains §11 and phase G.	2026-10-08 13:48:52 +02:00