From owner-freebsd-questions@FreeBSD.ORG Fri Oct 13 20:17:49 2006 Return-Path: X-Original-To: FreeBSD-Questions@freebsd.org Delivered-To: FreeBSD-Questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56A0C16A407 for ; Fri, 13 Oct 2006 20:17:49 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D50A43D96 for ; Fri, 13 Oct 2006 20:17:47 +0000 (GMT) (envelope-from dkelly@Grumpy.DynDNS.org) Received: (qmail 18235 invoked by uid 0); 13 Oct 2006 20:10:41 -0000 Received: from unknown (HELO Grumpy.DynDNS.org) (216.186.148.249) by smtp8.knology.net with SMTP; 13 Oct 2006 20:10:41 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id 20CF02840A; Fri, 13 Oct 2006 15:10:40 -0500 (CDT) Date: Fri, 13 Oct 2006 15:10:40 -0500 From: David Kelly To: Richard McIntyre Message-ID: <20061013201040.GA88241@Grumpy.DynDNS.org> References: <003a01c6ee0a$841e74f0$6908a8c0@pcmoperations> <20061012182206.GA81008@Grumpy.DynDNS.org> <452FE303.90002@tco2.thecompanyonline.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <452FE303.90002@tco2.thecompanyonline.com> User-Agent: Mutt/1.4.2.2i Cc: FreeBSD-Questions@freebsd.org Subject: Re: Hard Drive Issues 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, 13 Oct 2006 20:17:49 -0000 On Fri, Oct 13, 2006 at 03:03:31PM -0400, Richard McIntyre wrote: > David Kelly wrote: > > >On Thu, Oct 12, 2006 at 06:54:53PM +0100, Spiros Papadopoulos wrote: > > > >>Since as you say everything is working, maybe it is a good idea to > >>take a look and run the fsck command at least it may give you some > >>more information, which you can post in order to get better answers > > > >That too, but first I'd start with sysutils/smartmontools and see what > >the drive and its built-in log says. > > I'm having a similar problem, [...] > I'm guessing it will need to be replaced, output of smartctl is below.... [...] > SMART support is: Available - device has SMART capability. > SMART support is: Disabled Download the Seagate Tools CD, boot it, and enable SMART. Let the drive repair itself. Problem is that the problem has gone on long enough that the data in that block is totally lost. > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 40 51 04 c7 b6 d5 ea Error: UNC 4 sectors at LBA = 0x0ad5b6c7 = 181778119 What you need to do is figure out what file occupied that LBA and deal with its corruption. If part of the filesystem metadata then fsck will deal with it as best as can be. The Seagate tools will replace the bad block with a spare held in reserve. The spare will answer to the old's LBA. If SMART had been enabled in the first place the drive should have exchanged the block for a spare before the data was lost without bothering you. Doesn't always catch it in time. This sort of thing happens all the time. Thats why the tool is smart *mon*, its a monitor that you can watch inside the drive to see if its recovering from errors and on its last legs. Death is usually pronounced when the drive runs out of spare blocks for repair. Thats usually when a problem is first noticed. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.