From owner-freebsd-bugs@FreeBSD.ORG Thu Nov 27 22:57:04 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1C94ECC for ; Thu, 27 Nov 2014 22:57: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 6E835A3D for ; Thu, 27 Nov 2014 22:57: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 sARMv4M5064561 for ; Thu, 27 Nov 2014 22:57:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194522] smartmontools misbehaving (self-test timestamps do not match reality) Date: Thu, 27 Nov 2014 22:57:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed 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: Closed X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: 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: Thu, 27 Nov 2014 22:57:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194522 Jeremy Chadwick changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |Overcome By Events --- Comment #4 from Jeremy Chadwick --- Okay, strike that. It appears I was witnessing two separate issues simultaneously, which sounds crazy but seems to be the case after some further analysis. The first issue related to SMART attributes and self-test log entries affecting all drives in the system (Samsung SSD and several WD MHDD drives). That issue was rectified by power-cycling the system. This seems to imply the AHCI controller was experiencing some oddity/bug/quirk brought on by who-knows-what. After power-cycling, everything seemed fine -- except for the Samsung SSD. Which leads me to: The second issue relates to the Samsung drive and SMART attribute 9 vs. what the "LifeTime(hours)" field shows in a SMART self-test log entry. And I believe I've figured out what's going on there[1]: I recently updated my Samsung 840 EVO's firmware to fix a performance-related bug[2][3][4] that Samsung and many review sites found. It appears that after doing the firmware update, SMART attributes did not get reset back to zero/factory defaults, but "internal counters" used for calculating the power-on hour count within self-tests **did** get reset to 0. So there's now a permanent delta between SMART attribute 9 and the hour shown in a self-test log entry because of this mistake on Samsung's part. [1]: http://www.dslreports.com/forum/r29694516- [2]: http://www.computerworld.com/article/2836082/samsung-delivers-fix-for-ssd-slowdowns.html [3]: http://www.anandtech.com/show/8617/samsung-releases-firmware-update-to-fix-the-ssd-840-evo-read-performance-bug [4]: http://beta.slashdot.org/story/208795 So, we can close this out. There's nothing I can do about this newly-induced quirk in the Samsung firmware, and it obviously has nothing to do with FreeBSD. -- You are receiving this mail because: You are the assignee for the bug.