From owner-freebsd-hackers  Fri Aug 25 10:36:43 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id KAA19581
          for hackers-outgoing; Fri, 25 Aug 1995 10:36:43 -0700
Received: from cs.weber.edu (cs.weber.edu [137.190.16.16])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id KAA19575
          for <hackers@freefall.FreeBSD.org>; Fri, 25 Aug 1995 10:36:42 -0700
Received: by cs.weber.edu (4.1/SMI-4.1.1)
	id AA11968; Fri, 25 Aug 95 11:38:14 MDT
From: terry@cs.weber.edu (Terry Lambert)
Message-Id: <9508251738.AA11968@cs.weber.edu>
Subject: Re: ESDI drive woes
To: peter@nmti.com (Peter da Silva)
Date: Fri, 25 Aug 95 11:38:13 MDT
Cc: hackers@freefall.FreeBSD.org
In-Reply-To: <9508250655.AA11449@sonic.nmti.com.nmti.com> from "Peter da Silva" at Aug 25, 95 01:55:35 am
X-Mailer: ELM [version 2.4dev PL52]
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.

WD1007 format utility on ftp.wdc.com.


					Terry Lambert
					terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.