backdown

backdown health

How each drive is doing: SMART verdict, temperature, bad sectors, wear, and what changed since its first reading (read now, without root; kept in the index). Exits 2 when a connected drive is failing.

On this page
backdown health [OPTIONS]

Options

--json
Print it as JSON, for scripts.
--machines
The other machines' drives instead (Team), as each one's own BackDown last read them, fetched with its last sync: nothing is reached or read now. Exits 2 when a drive there is failing.

Also takes the global options --db and --local.

Good to know

Reads each drive's own health reports (SMART) as you, without administrator rights: through udisks (and smartctl where your account may use it) on Linux, diskutil (and smartctl, if installed) on macOS, and the storage cmdlets on Windows, which share error counters only with an administrator. smartctl is asked not to wake a drive that has spun down. What can't be read is noted, with the command that would read it. Readings are kept in the index under the drive's serial number, so its history follows it from port to port. When the daemon runs (Linux and macOS), health has it read every drive now; it also reads them every six hours, when a drive appears and when an indexed drive comes back. No self-tests are run. Exits 2 when a connected drive is failing.

Examples

backdown health
# in a script: 2 = a connected drive is failing
backdown health --json > health.json

See also

Last updated · What's released, and what's next