From owner-freebsd-questions@FreeBSD.ORG Mon Mar 7 08:55:37 2005 Return-Path: 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 77FA516A4CE for ; Mon, 7 Mar 2005 08:55:37 +0000 (GMT) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00C6D43D2D for ; Mon, 7 Mar 2005 08:55:37 +0000 (GMT) (envelope-from tedm@toybox.placo.com) Received: from tedwin2k (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) j278tQb52763; Mon, 7 Mar 2005 00:55:26 -0800 (PST) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Doug Hardie" , "Aftab Jahan Subedar" Date: Mon, 7 Mar 2005 00:55:19 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <3b4c464a28f9ab1219026ff6f40faf04@lafn.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Importance: Normal cc: FreeBSD Questions Subject: RE: Disk Error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2005 08:55:37 -0000 > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Doug Hardie > Sent: Sunday, March 06, 2005 10:24 PM > To: Aftab Jahan Subedar > Cc: FreeBSD Questions > Subject: Re: Disk Error > > > I doubt that its dying. There is only one bad sector. The > drive is in > constant use. Its ran at 100% for almost 12 hours while copying the > files and no errors were detected. Its always the same sector > with the > error. > I've seen something like this once when a drive/bios combo lied about the number of blocks the drive had available. The BSD partition was created larger than the actual available blocks, thus whenever the OS sent data to blocks that didn't exist, you got this problem. If this is setup OK then as the other poster said your days on this drive are coming to an end. IDE drives have a number of reserved blocks available that are used internally by the drive to map out bad sectors. When a drive starts going bad the sectors start failing one by one and the drive maps them out - when it uses up all the reserved blocks then the drive starts returning errors to the operating system. If this drive supports S.M.A.R.T. and it's enabled and your running 5.X then smartmon might give you some data about the actual real state of the drive, rather than the lies that the drive normally tells the OS. Ted