From owner-freebsd-questions@FreeBSD.ORG Fri Jan 6 06:52:55 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D201106567D for ; Fri, 6 Jan 2012 06:52:55 +0000 (UTC) (envelope-from b.smeelen@ose.nl) Received: from mail.ose.nl (mail.ose.nl [212.178.134.164]) by mx1.freebsd.org (Postfix) with ESMTP id ABB998FC1A for ; Fri, 6 Jan 2012 06:52:54 +0000 (UTC) X-Footer: b3NlLm5s Received: from localhost ([127.0.0.1]) by mail.ose.nl (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits)) for freebsd-questions@freebsd.org; Fri, 6 Jan 2012 07:52:52 +0100 Message-ID: <4F069A44.7020600@ose.nl> Date: Fri, 06 Jan 2012 07:52:52 +0100 From: Bas Smeelen User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20120105144204.d419cca4.web@3dresearch.com> <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> In-Reply-To: <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Apparently conflicting smartctl output X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2012 06:52:55 -0000 On 01/05/2012 08:56 PM, Chuck Swiger wrote: > On Jan 5, 2012, at 11:42 AM, Janos Dohanics wrote: >> - Do I have a bad hard drive (apparently, I do...) >> >> - Why are there "No Errors Logged" by smartctl? > You've probably got a bad sector on the drive, anyway. > > The SMART error log is a funny thing governed by various drive's firmware which have quirks. Some of 'em only have a self-test log, but don't store the error log at all; others will only record an error after they've given up trying to remap a failing sector. You snipped too much of the smartctl output to see what the "Error logging capability" section says-- the full output would be more informative. > > You almost certainly want to do a full read-scan of the drive via "dd if=/dev/ad4 of=/dev/null bs=64k", which will help the drive notice any other failing sectors. Repeat dd if it aborts early with an error (or add "conv=noerror", maybe). > > Regards, Hi, I have had this with a drive and multiple read errors would not remap the sector. With write errors the sector would be remapped. This was a new Samsung laptop drive though, not a Western Digital. To get the sector remapped I had to fully write the drive and it was ok after that. For now no bad sectors have been showing up Disclaimer: http://www.ose.nl/email