Date: Thu, 05 Jan 2012 11:56:44 -0800 From: Chuck Swiger <cswiger@mac.com> To: Janos Dohanics <web@3dresearch.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Apparently conflicting smartctl output Message-ID: <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> In-Reply-To: <20120105144204.d419cca4.web@3dresearch.com> References: <20120105144204.d419cca4.web@3dresearch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6ABAC46B-6193-47B6-B173-94D060E01EC4>