From owner-freebsd-hackers  Sat Jun 15 09:01:41 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA01512
          for hackers-outgoing; Sat, 15 Jun 1996 09:01:41 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA01502
          for <hackers@freebsd.org>; Sat, 15 Jun 1996 09:01:38 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id JAA20614; Sat, 15 Jun 1996 09:01:25 -0700 (PDT)
To: Yves Lepage <yves@CC.McGill.CA>
cc: hackers@freebsd.org, yves@maelstrom.CC.McGill.CA
Subject: Re: IBM HD's 
In-reply-to: Your message of "Sat, 15 Jun 1996 11:25:53 EDT."
             <199606151525.LAA18470@maelstrom.CC.McGill.CA> 
Date: Sat, 15 Jun 1996 09:01:25 -0700
Message-ID: <20612.834854485@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> - Quantum Fireball

I can also verify this one - we had a machine at the office with one
of these drives in it (before it was torn apart for scrap :-) and we
never could get FreeBSD to install on it.  Exact same symptoms.

I never did figure out what was going on and the machine is history
now so I never will..  Hmmmm.  I wonder if the output of `boot -v'
would be helpful.  FreeBSD is clearly not happy with its attempts to
write on this drive, there must be something "special" about it!

					Jordan