From owner-freebsd-questions@FreeBSD.ORG Fri Jan 6 17:27:16 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 28796106566C for ; Fri, 6 Jan 2012 17:27:16 +0000 (UTC) (envelope-from web@3dresearch.com) Received: from smtp.3dresearch.com (dorabella.3dresearch.com [66.167.251.2]) by mx1.freebsd.org (Postfix) with ESMTP id B2ACA8FC15 for ; Fri, 6 Jan 2012 17:27:15 +0000 (UTC) Received: from fracasso.3dresearch.com (pool-96-236-174-150.pitbpa.east.verizon.net [96.236.174.150]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vmail.3dresearch.com (Postfix) with ESMTP id 78A7586A25; Fri, 6 Jan 2012 12:27:12 -0500 (EST) Received: from fracasso.3dresearch.com (localhost [127.0.0.1]) by fracasso.3dresearch.com (Postfix) with SMTP id 55A3B5C5D; Fri, 6 Jan 2012 12:27:10 -0500 (EST) Date: Fri, 6 Jan 2012 12:22:25 -0500 From: Janos Dohanics To: Chuck Swiger Message-Id: <20120106122225.69ee46d2.web@3dresearch.com> In-Reply-To: <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> References: <20120105144204.d419cca4.web@3dresearch.com> <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> X-Mailer: Sylpheed 3.1.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions 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 17:27:16 -0000 On Thu, 05 Jan 2012 11:56:44 -0800 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, > -- > -Chuck Chuck, Thank you - dd says: dd: /dev/ad4: Input/output error 10025840+0 records in 10025840+0 records out 657053450240 bytes transferred in 5230.204427 secs (125626724 bytes/sec) I have to replace this drive. -- Janos Dohanics