Scrutiny
Scrutiny: a first setup, important settings, verification, and recovery considerations.
Working directory: ~/homelab/ops/storage-health. Follow the common setup workflow first. This is a setup note based on the linked documentation, not a copy of my live configuration or a runtime verification of this full stack.
Start here
Scrutiny collects disk-health information such as SMART attributes. Read its official container and collector requirements before granting hardware access. Begin by identifying one spare or practice disk. A virtual machine may not expose physical SMART data, and some USB bridges hide it.
Settings and data
The collector needs access to selected devices and specific host capabilities. Limit these to what the documented installation requires; do not expose every block device by habit. Persist the dashboard/database state according to the chosen all-in-one or separate deployment. Device names can change across boots, so record stable identities privately.
Check it
Run the documented collection step and confirm the intended disk model appears with fresh readings. Compare a reported value with a read-only SMART inspection on the host. Do not run destructive disk tests, formatting, or an intensive self-test on an unplanned production drive.
When something fails
Missing metrics may mean unsupported passthrough rather than a healthy or failed disk. Review collector errors and device mapping. A passing SMART result is not a guarantee against sudden failure. Use this alongside backups, capacity monitoring, and a tested replacement/recovery procedure. Disk serial numbers do not belong in public screenshots.