From owner-freebsd-bugs@FreeBSD.ORG Wed Oct 22 00:35:04 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD978490 for ; Wed, 22 Oct 2014 00:35:04 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B053765 for ; Wed, 22 Oct 2014 00:35:04 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s9M0Z4lI039091 for ; Wed, 22 Oct 2014 00:35:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194522] New: smartmontools misbehaving Date: Wed, 22 Oct 2014 00:35:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jdc@koitsu.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2014 00:35:04 -0000 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@FreeBSD.org Reporter: jdc@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.