From owner-freebsd-hardware Fri Dec 12 03:11:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA11596 for hardware-outgoing; Fri, 12 Dec 1997 03:11:53 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from nexos.com.br (ns.nexos.com.br [200.239.191.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA11543 for ; Fri, 12 Dec 1997 03:10:26 -0800 (PST) (envelope-from josue@compacto.nexos.com.br) Received: from compacto.nexos.com.br (compacto.nexos.com.br [192.168.0.4]) by nexos.com.br (8.8.5/8.8.5) with ESMTP id JAA06724; Fri, 12 Dec 1997 09:09:21 -0200 (EDT) Received: from localhost (josue@localhost) by compacto.nexos.com.br (8.8.5/8.8.5) with SMTP id JAA03510; Fri, 12 Dec 1997 09:09:00 -0200 (EDT) Date: Fri, 12 Dec 1997 09:08:54 -0200 (EDT) From: "Josué José Souza Jr." To: Bruce Evans cc: freebsd-hardware@freebsd.org Subject: Re: Bad144 In-Reply-To: <199712111529.CAA14239@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Dec 1997, Bruce Evans wrote: > >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. Is it safe to install the FreeBSD without using bad144 to scan the drive? What I mean is: does FreeBSD 2.2.5 uses ATA's bios capability of mapping bad blocks? And I didn't understand how can the slice size could be wrong since I'm not using fdisk directly to make them but the install program itself. > > >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. I didn't understand this. If the modern drives do the bad block mapping by themself, why can't I just ignore the warning or skip bad block scan? > > >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 > Thanks in advance, ------------------- Josue Souza Jr. josue@nexos.com.br joshua@svn.com.br -------------------