From owner-freebsd-hackers  Fri Aug 25 09:35:28 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id JAA14985
          for hackers-outgoing; Fri, 25 Aug 1995 09:35:28 -0700
Received: from uuneo.neosoft.com (uuneo.NeoSoft.COM [198.64.84.252])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id JAA14979
          for <hackers@freefall.FreeBSD.org>; Fri, 25 Aug 1995 09:35:27 -0700
Received: from ris1.UUCP (ficc@localhost) by uuneo.neosoft.com (8.6.10/8.6.10) with UUCP id LAA15144 for freefall.cdrom.com!hackers; Fri, 25 Aug 1995 11:23:03 -0500
Received: by ris1.nmti.com (smail2.5)
	id AA18557; 25 Aug 95 01:29:57 CDT (Fri)
Received: by sonic.nmti.com; id AA11449; Fri, 25 Aug 1995 01:55:36 -0500
From: peter@nmti.com (Peter da Silva)
Message-Id: <9508250655.AA11449@sonic.nmti.com.nmti.com>
Subject: ESDI drive woes
To: hackers@freefall.FreeBSD.org
Date: Fri, 25 Aug 1995 01:55:35 -0500 (CDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 719       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

OK, I'm trying for the umpteenth time to install FreeBSD 2.0.5 on an
ESDI drive.

Drive is formatted with Disk Manager.

Apparently when Disk Manager sees a bad sector, it "spares" the whole track.
Unfortunately, FreeBSD doesn't know where to find the spare track, or the
spare track is unformatted. Disk Manager won't format outside the official
data space on the drive.

When bad144 sees a spare track, it eats all 35 of the sectors on it and
it doesn't take many defects to beat the maximum of 126 defects per
partition at that rate.

The controller is an HP special. It looks like a WD1007 but doesn't appear
to have a BIOS accessible through DEBUG, so I can't use the WD sector
sparing even if I wanted to.

Help?