From owner-freebsd-hardware  Thu Mar 13 08:40:19 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA06118
          for hardware-outgoing; Thu, 13 Mar 1997 08:40:19 -0800 (PST)
Received: from seine.cs.umd.edu (seine.cs.umd.edu [128.8.128.59])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA06108
          for <hardware@freebsd.org>; Thu, 13 Mar 1997 08:40:16 -0800 (PST)
Received: by seine.cs.umd.edu (8.8.5/UMIACS-0.9/04-05-88)
	id LAA23867; Thu, 13 Mar 1997 11:40:14 -0500 (EST)
Message-Id: <199703131640.LAA23867@seine.cs.umd.edu>
To: hardware@freebsd.org
cc: Rodney Grimes <rgrimes@gndrsh.aac.dev.com>
Subject: RE: dump / dd / amdump crashing FreeBSD 2.1.5 / 2.2 machines
Date: Thu, 13 Mar 1997 11:40:13 -0500
From: Rohit Dube <rohit@cs.umd.edu>
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I missed out one piece of information from the previous post. Ouch. Sorry.

Thanks.
--rohit.

--->
Unfortunately, the problem also exists in 2.1.5 - Running a dd from /dev/rsd0
to /dev/null under the 2.1.5 fixit disk causes the disk to drop out the same
way, though the error messages are not as drastic: the i/o errors out with
an i/o error, but every other attempt to access the disk claims it is not
configured.  As with 2.2, after resetting following this occurance, the disk
is not visible even to the Adaptec probe on boot-up.  I must power-cycle.

The block position where the error is triggered varies, by the way.

Jaime
<---