|
|
|
@ -113,11 +113,25 @@ instead of the block device (`/dev/nvme0n1`). See [#209](https://github.com/Anal
|
|
|
|
|
|
|
|
|
|
### ATA
|
|
|
|
|
|
|
|
|
|
### USB Devices
|
|
|
|
|
|
|
|
|
|
The following information is extracted from [#266](https://github.com/AnalogJ/scrutiny/issues/266)
|
|
|
|
|
|
|
|
|
|
External HDDs support two modes of operation usb-storage (old, slower, stable) and uas (new, faster, sometimes unstable)
|
|
|
|
|
. On some external HDDs, uas mode does not properly pass through SMART information, or even causes hardware issues, so
|
|
|
|
|
it has been disabled by the kernel. No amount of smartctl parameters will fix this, as it is being rejected by the
|
|
|
|
|
kernel. This is especially true with Seagate HDDs. One solution is to force these devices into usb-storage mode, which
|
|
|
|
|
will incur some performance penalty, but may work well enough for you. More info:
|
|
|
|
|
|
|
|
|
|
- https://smartmontools.org/wiki/Supported_USB-Devices
|
|
|
|
|
- https://smartmontools.org/wiki/SAT-with-UAS-Linux
|
|
|
|
|
- https://forums.raspberrypi.com/viewtopic.php?t=245931
|
|
|
|
|
|
|
|
|
|
### Exit Codes
|
|
|
|
|
|
|
|
|
|
If you see an error message similar to `smartctl returned an error code (2) while processing /dev/sda`, this means that
|
|
|
|
|
`smartctl` (not Scrutiny) exited with an error code. Scrutiny will attempt to print a helpful error message to help you debug,
|
|
|
|
|
but you can look at the table (and associated links) below to debug `smartctl`.
|
|
|
|
|
`smartctl` (not Scrutiny) exited with an error code. Scrutiny will attempt to print a helpful error message to help you
|
|
|
|
|
debug, but you can look at the table (and associated links) below to debug `smartctl`.
|
|
|
|
|
|
|
|
|
|
> smartctl Return Values
|
|
|
|
|
> The return values of smartctl are defined by a bitmask. If all is well with the disk, the return value (exit status) of
|
|
|
|
|