From owner-freebsd-stable@FreeBSD.ORG Wed Oct 15 05:08:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6996D16A4B3 for ; Wed, 15 Oct 2003 05:08:55 -0700 (PDT) Received: from mta07-svc.ntlworld.com (mta07-svc.ntlworld.com [62.253.162.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B9B043F3F for ; Wed, 15 Oct 2003 05:08:54 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.124]) by mta07-svc.ntlworld.comESMTP <20031015120853.YGIP2637.mta07-svc.ntlworld.com@llama.fishballoon.org>; Wed, 15 Oct 2003 13:08:53 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 1A9kRh-0004sf-5y; Wed, 15 Oct 2003 13:08:05 +0100 Date: Wed, 15 Oct 2003 13:08:05 +0100 From: Scott Mitchell To: Kevin Oberman Message-ID: <20031015120805.GA16087@llama.fishballoon.org> References: <20031014085554.GC84877@llama.fishballoon.org> <20031014160214.C51925D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031014160214.C51925D07@ptavv.es.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE-p13 i386 Sender: Scott Mitchell cc: freebsd-stable@freebsd.org Subject: Re: ATA failure with 4.6.2 & 250GB drive? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 12:08:55 -0000 Hi Kevin, As always, a most enlightening response :-) On Tue, Oct 14, 2003 at 09:02:14AM -0700, Kevin Oberman wrote: > It's a real drive problem, but possibly not a terminal one. (I had the > same issue on one of my drives a few months ago and it's fine now.) ... > The fix/workaround is to move the file(s) involved so that the damaged > blocks are marked free and relocated to spar space on the drive. You > can try to figure out just which file(s) use those blocks. There > might even be a reasonable way to do this...I just don't know what it > is. > > Another "fix"is to simply copy the drive onto another and then copy it > back. dd(1) will do the trick as will dump/restore. (I'd suggest the > dump/restore to copy the data out and dd to copy it back if the disks > have identical geometries.) Once the data is restored to the original > disk, the bad blocks will have been re-directed by the drive and will > no longer trouble you. I'll probably pull it out and run the Maxtor diagnostics over it to see if they turn up anything interesting. Do you think a low-level format would be useful? Very annoying to have two of these things die almost immediately after installation. Does not encourage me to buy more Maxtor products in the future :-( Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott at fishballoon.org | 0xAA775B8B | -- Anon