smartctl thinks Hitachi and Toshiba drives are failing if it doesn't set the device type when querying the drive #1016
rmohns
started this conversation in
Issue Triage
Replies: 1 comment
-
|
Can you please share the debug logs from the collector? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Issue Description
It appears that smartctl has trouble with some Hitachi and Toshiba drives, and must be explicitly told their device type in order to get correct values. Auto or not specified results in a SMART status of Failing. This, in turn, causes Scrutiny to report it failing and report zeros for all SMART values.
Here's an example of the failure mode:
And here it is with the device type specified (SATA, in this case):
See also issue #618
FWIW, it appears that the scrutiny fork by Starosdev has solved this, but I am not qualified to go digging into it to find out what they did.
Expected Behavior
Correct smart data should be ready from the disk.
Actual Behavior
smartctl reports SMART failure and doesn't read any SMART data.
Reproduction Steps
scrutiny debug logs
No response
Scrutiny Version
v0.9.2
Smartmontools Version
docker
OS Version Information
Docker on Synology NAS (Intel)
Component
collector
Deployment Method
Hard Drive Information
Toshiba N300 Pro, model HDWG51GUZSVB
smartctl output
docker-compose.yml
scrutiny.yaml
(I don't have one.)collector.yaml
Additional relevant configuration
I acknowledge that:
```) on separate lines.Beta Was this translation helpful? Give feedback.
All reactions