From owner-freebsd-questions@FreeBSD.ORG Thu Nov 19 01:53:14 2009 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 32D6C1065670 for ; Thu, 19 Nov 2009 01:53:14 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 139AE8FC17 for ; Thu, 19 Nov 2009 01:53:13 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 7C768BDC46 for ; Wed, 18 Nov 2009 17:53:12 -0800 (PST) To: freebsd-questions@freebsd.org In-Reply-To: <44my2n45zd.fsf@be-well.ilk.org> Date: Wed, 18 Nov 2009 17:53:12 -0800 Message-ID: <80459.1258595592@tristatelogic.com> From: "Ronald F. Guilmette" Subject: Re: Bad Blocks... Should I RMA? 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, 19 Nov 2009 01:53:14 -0000 In message <44my2n45zd.fsf@be-well.ilk.org>, Lowell Gilbert wrote: >"Ronald F. Guilmette" writes: > >> Nov 15 15:24:17 coredump kernel: ad4: FAILURE - READ_DMA status=51,ERROR> error=40 LBA=256230591 > >This is *not* necessarily a big deal, despite what your other response >told you. Errors on reads do not mean that your drive's bad-sector >table is full; only errors on write indicate that. If you can try >manufacturer's drive diagnostics, do that. If you can't, then it's >harder to fix things up, but not impossible; write back if you >really can't use a low-level diag. Well, OK, so I ran the "long test" in Seagate Seatools. Result: It noticed exactly and only _one_ bad sector, which I of course told it to repair/remap. The kicker: The specific bad secror was somewhat near to the one that was indicated in the FreeBSD /var/log/messages errors, _however_ it was most definitely a different LBA sector #. So at that point I was kinda worried, cuz now I was looking at two bad sectors. Still, I didn't really want to have to RMA a drive that's less than one year old, so I used dd and copied /dev/zero to the whole drive. Then I used dd again to copy the wole drive to /dev/null. No errors at all in either case. Then I ran the Seatools "long" diagnostic again. Result: Zero errors. So I decided to keep the drive. Yes, there's some bad sectors, but I think they are all locked out now. I'm hoping this isn't a mistake. Only time will tell. Regards, rfg