4 Commits

Include renames

Author	SHA1	Message	Date
jochen	7aba612c6c	sensors: take a SAS drive's standby, whose mode holds spaces ... The third review found the asleep match took only one-word modes, so a SAS drive in STANDBY BY TIMER or LOW POWER was read as a failed answer and lost its reading.	2026-10-08 15:04:02 +02:00
jochen	66a816c3ac	sensors: say a stuck drive read, and be the drives' only reader ... The second review of #129 found a read stuck in the kernel kept the file fresh and the module healthy, smartd as a second reader could wake or keep awake the drives the watch spares, and a board chip's maximum could stop a fan. Read each drive in its own goroutine from a root reader of the module's own, mark each read in flight, and say a read past its bound or a drive not looked at for twice its cadence; drop smartd; tell smartctl each drive's kind; take a SAS drive's standby; say a drive asleep since when.	2026-10-08 14:59:10 +02:00
jochen	66a32b196d	sensors: raise only what the hardware says is failing, and say a hung watch ... The review of #129 found false alarms and a silent failure: the NVMe temperature bit, old-age attributes, a fan's minimum or latched alarm, an unrelated hot sensor and a board chip's limits could raise a condition, while a hung smartctl stopped the fans' looks and an old readings file passed as healthy. Read spinning drives hourly (smartd too) so a read never keeps one from spinning down, and skip a drive that cannot say whether it sleeps.	2026-10-08 14:35:16 +02:00
jochen	73610f8e3c	sensors: read the machine's hardware condition on every machine (hq ADR 0256) ... Temperatures against the hardware's own thresholds, fans, each drive's health and the kernel's error counts, read-only. A root watch reads SMART so the tools need no root and never wake a sleeping drive; smartd and the watch carry the health that raises a condition when the hardware says it is failing.	2026-10-08 13:48:53 +02:00