v1.67.1 (2026-07-28)
Bug Fixes
-
Preserve jmb39x-q device type and accept usable SMART JSON (#677) - Fixes #663
- QNAP TR-004 enclosures in Individual mode address each bay through the smartmontools jmb39x-q,N backend. Two independent collector defects made those disks unmonitorable. Both are fixed here.
-
Pass explicitly configured smartctl device types verbatim (#678) - Fixes #664
- Some Hitachi and Toshiba drives answer an auto-detected smartctl query with no identity, SMART support is: Unavailable and no attributes. Scrutiny renders that as a failed disk with zero metrics. The documented remedy is to pin the device type in collector.yaml; for most of these drives that type is sat, which already reached smartctl. A configured type of scsi or ata did not.
- All three smartctl call sites (detection --info, collection --xall, FARM log) carried a hand-copied guard:
- go
- if len(deviceType) > 0 && deviceType != "scsi" && deviceType != "ata" {
- args = append(args, "--device", deviceType)
- }
- The guard is correct for a type that came from smartctl --scan: container scans routinely mislabel ATA disks as SCSI, and forcing -d scsi on one loses its ATA attributes. It is wrong for a type the user wrote down, but models.Device carries no provenance, so the two were indistinguishable. The comparison was also exact-case, so type: 'ATA' was passed through while type: 'ata' was dropped.