From owner-freebsd-hardware Thu Dec 11 07:34:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA20408 for hardware-outgoing; Thu, 11 Dec 1997 07:34:41 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA20402 for ; Thu, 11 Dec 1997 07:34:37 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id CAA14239; Fri, 12 Dec 1997 02:29:56 +1100 Date: Fri, 12 Dec 1997 02:29:56 +1100 From: Bruce Evans Message-Id: <199712111529.CAA14239@godzilla.zeta.org.au> To: freebsd-hardware@freebsd.org, josue@compacto.nexos.com.br Subject: Re: Bad144 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hello. I'm new on this list and I'm having a problem installing the >FreeBSD 2.2.5. The problem is: when bad144 scans the HD for bad >blocks, it says that there are too many bad blocks on the slice and >that it can handle only 126 bad blocks per slice. I tried making three >slices, but the last one always shows this problem. I tried the following >HDs: >Maxtor model 83240D4, 6696 Cyl, 15 Heads, 63 Sectors >Seagate model ST3320A, 6253 Cyl, 16 Heads, 63 Sectors bad144 is normally only used for old MFM and ESDI drives, since modern drives remap bad blocks themself so that they appear to haeve 0 bad blocks. Perhaps the slice size is wrong. >1. Does the bad144 have some kind of incompatibility with these HDs? Old versions (from yesterday) couldn't handle slices larger than 2G. >2. Is there any problem in continuing the install process, even with the >bad144 warning? Probably. >3. Is there another program similar to bad144 that could handle more than >126 bad blocks per slice? I know the badsect but it doesn't does the full >HD test. No. Bruce