[Bug 194522] New: smartmontools misbehaving
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Oct 22 00:35:04 UTC 2014
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194522
Bug ID: 194522
Summary: smartmontools misbehaving
Product: Base System
Version: 9.2-STABLE
Hardware: amd64
OS: Any
Status: Needs Triage
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-bugs at FreeBSD.org
Reporter: jdc at koitsu.org
Created attachment 148554
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148554&action=edit
dmesg.txt
NOTE: FreeBSD version involved is technically 9.3-STABLE, but the Bugzilla GUI
only offers up to 9.3-RELEASE. Rephrased: I run base/stable/9.
I'm filing this PR in combination or relation to an open ticket I filed with
the smartmontools folks:
http://www.smartmontools.org/ticket/466
Full details, including all output and lots of examples, are there.
Basically, there is something going on within FreeBSD (or possibly within
smartmontools, although rebuilding smartmontools 6.2 and using that shows the
same problems) where certain SMART attribute values do not seem to
appear/behave correctly when compared to values in the SMART extended self-test
log. The issue is 100% reproducible, and cannot be reproduced on Windows.
Specifically, a self-test issued at a certain Power_On_Hours count does not
appear that way -- e.g. if Power_On_Hours is 12345 and a self-test is run, the
SMART extensive self-test log might show the test completed at time 12189, or
possibly sometime in the future.
This issue affects multiple models of MHDDs and SSDs, and makes data recovery
and diagnostics extremely difficult given the behaviour.
The ATA CDBs being submit to the drive + full response payload I can try to get
using CAM debugging, but I at least wanted to file a PR on the matter because
at this point it's looking to be FreeBSD-centric in some way.
I'll attach dmesg output, as well as pciconf -lvbc output.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list