From owner-freebsd-questions Sun Jul 14 16:21:51 2002 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 56C3837B400 for ; Sun, 14 Jul 2002 16:21:48 -0700 (PDT) Received: from mail.samuelstn.dhs.org (h24-64-81-248.cg.shawcable.net [24.64.81.248]) by mx1.FreeBSD.org (Postfix) with SMTP id C965E43E4A for ; Sun, 14 Jul 2002 16:21:46 -0700 (PDT) (envelope-from cyschow@shaw.ca) Received: (qmail 90620 invoked from network); 14 Jul 2002 23:21:41 -0000 Received: from celeron (192.168.1.6) by homeserver with SMTP; 14 Jul 2002 23:21:41 -0000 Message-ID: <00f101c22b8d$36348570$0601a8c0@samuelstn.dhs.org> From: "Samuel Chow" To: "Joshua Lokken" Cc: "FreeBSD Questions" References: Subject: Re: installing BSD Date: Sun, 14 Jul 2002 17:21:41 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Joshua Lokken said: > > > The 'hard error' pretty much indicates a bad disk. > > Since the bad track (tn = 13) is at the beginning of > > the disk, you might want to try to create a small FAT > > slice to skip the bad track. > > > > If I were you, I would go buy and replace this dying > > disk. > > In regards to your answer to this persons question, if I have a drive that I > know has some bad blocks, first, if I map the drive to skip these blocks, how > reliable is said drive, and second, how would I go about mapping the bad > blocks with FreeBSD (which utility)? Thanks in advance for any help you > can give. From my understanding, IDE drives reserve certain space to remap bad blocks automatically. For this error to show up, all the spare space must have been used up. It also means that the drive is not able to deal with any new errors, and therefore any new errors will probably lead to filesystem corruption. If you value your time and data, I would strongly suggest you replace any drive showing errors. --- Samuel Chow cyschow@shaw.ca Segmentation Fault (core dumped) This message is displayed using recycled electrons. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message