From owner-freebsd-questions  Sun Jun 22 19:58:55 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA06911
          for questions-outgoing; Sun, 22 Jun 1997 19:58:55 -0700 (PDT)
Received: from fnord.i33.com (fnord.i33.com [207.111.105.32])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA06902
          for <questions@freebsd.org>; Sun, 22 Jun 1997 19:58:50 -0700 (PDT)
Received: from fnord.i33.com ([127.0.0.1]) by fnord.i33.com
          (Netscape Mail Server v2.02) with SMTP id AAA29195
          for <questions@freebsd.org>; Sun, 22 Jun 1997 22:03:32 -0400
Message-ID: <19970622220331.25686@i33.com>
Date: Sun, 22 Jun 1997 22:03:31 -0400
From: "Amir Y. Rosenblatt" <amir@i33.com>
To: questions@freebsd.org
Subject: dump problem [2.2.1]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.75
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Background:

I was running 2.2.1-STABLE and had a disk crash on my boot disk.  Put in a
new disk, did a fresh install on that disk to cinfigure it, then restored
the contents of the original to it.  However, now when Iattempt a file
system dump I get the following error:

  DUMP: Date of this level 0 dump: Sun Jun 22 05:00:00 1997
  DUMP: Date of last level 0 dump: the epoch
  DUMP: Dumping /dev/rwd0a (/) to /dev/nrst0
  DUMP: mapping (Pass I) [regular files]
  DUMP: mapping (Pass II) [directories]
  DUMP: estimated 33365 tape blocks on 0.01 tape(s).
  DUMP: dumping (Pass III) [directories]
  DUMP: write error 64 blocks into volume 1
  DUMP: fopen on /dev/tty fails: Device not configured
  DUMP: The ENTIRE dump is aborted.

Additionally, at the same time, /var/log/messages gets hit with the
following (the tape drive is SCSI, hooked to an Adaptec 2940UW):

Jun 21 05:02:05 prozac /kernel: sd0(ahc0:1:0): UNIT ATTENTION asc:29,0
Jun 21 05:02:05 prozac /kernel: sd0(ahc0:1:0):  Power on, reset, or bus
device reset occurred field replaceable unit: 1
Jun 21 05:02:05 prozac /kernel: , retries:4
Jun 21 05:02:27 prozac /kernel: sd0(ahc0:1:0): SCB 0x2 - timed out in
dataout phase, SCSISIGI == 0x4
Jun 21 05:02:27 prozac /kernel: SEQADDR = 0x124 SCSISEQ = 0x12 SSTAT0 =
0x0 SSTAT1 = 0x2
Jun 21 05:02:27 prozac /kernel: st0(ahc0:3:0): abort message in message buffer
Jun 21 05:02:27 prozac /kernel: st0(ahc0:3:0): SCB 1 - Abort Completed.
Jun 21 05:02:27 prozac /kernel: st0(ahc0:3:0): no longer in timeout
Jun 21 05:04:07 prozac /kernel: st0(ahc0:3:0): SCB 0x1 - timed out while idle, 
LASTPHASE == 0x1, SCSISIGI == 0x0
Jun 21 05:04:07 prozac /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5
SSTAT1 = 0xa
Jun 21 05:04:07 prozac /kernel: st0(ahc0:3:0): SCB 1: Immediate reset.
 Flags = 0x1
Jun 21 05:04:07 prozac /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted
Jun 21 05:04:07 prozac /kernel: Clearing bus reset
Jun 21 05:04:07 prozac /kernel: Clearing 'in-reset' flag
Jun 21 05:04:07 prozac /kernel: st0(ahc0:3:0): no longer in timeout

etc...

The system config is as follows:

- Tyan dual PPro motherboard with a single PPro 200
- Adaptec 2940UW
- Boot disk: 4 gig Maxtor IDE
- A pair of Seagate ST32550W 2.1 gig Baraccudas as the second and third
  disks.
- 96 meg RAM
- Number 9 Imagine 128 4 meg video card/  
- 3Com 3c509B-TP ethernet card


I was intending to move to 2.2.2 but I don't feel comfortable doing a make
world without backing the system up.  

Thanks in abundance,

	-Amir