From owner-freebsd-questions@FreeBSD.ORG Thu Jan 5 19:56:54 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 7CC17106566B for ; Thu, 5 Jan 2012 19:56:54 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout030.mac.com (asmtpout030.mac.com [17.148.16.105]) by mx1.freebsd.org (Postfix) with ESMTP id 630E78FC14 for ; Thu, 5 Jan 2012 19:56:54 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from cswiger1.apple.com (unknown [17.209.4.71]) by asmtp030.mac.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPSA id <0LXC00CROCQLRS70@asmtp030.mac.com> for freebsd-questions@freebsd.org; Thu, 05 Jan 2012 11:56:45 -0800 (PST) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110,1.0.211,0.0.0000 definitions=2012-01-05_05:2012-01-05, 2012-01-05, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1201050222 From: Chuck Swiger In-reply-to: <20120105144204.d419cca4.web@3dresearch.com> Date: Thu, 05 Jan 2012 11:56:44 -0800 Message-id: <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> References: <20120105144204.d419cca4.web@3dresearch.com> To: Janos Dohanics X-Mailer: Apple Mail (2.1084) 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: Thu, 05 Jan 2012 19:56:54 -0000 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