# Disks present but SMART is unreadable

- Rule ID: `drive_smart_unreadable`
- Priority: P2
- Category: Storage
- Page: https://glassmkr.com/docs/rules/drive_smart_unreadable

## What it means

One or more fixed disks are present but their SMART health cannot be read, so their health is invisible to monitoring. This is NOT a drive fault: it is a coverage gap. The usual cause is that smartmontools (the `smartctl` binary) is not installed, or a disk sits behind a RAID/HBA controller that needs a specific `smartctl -d` device type. While SMART is unreadable, a real failure on the affected disks would not raise smart_failing or wear alerts.

Fix by installing smartmontools and confirming each disk reads with `smartctl -H`, or by determining the controller's device type (`smartctl --scan-open`). Acknowledge this advisory if a listed device genuinely exposes no SMART (some virtual or enclosure devices).


## Remediation

Every rule ships a distro-aware remediation workflow: prerequisites, the
command to run, how to verify it worked, and how to roll it back. Those are
instructions for an operator. Glassmkr does not execute them for you.
The workflow for this rule is on its page: https://glassmkr.com/docs/rules/drive_smart_unreadable