From owner-freebsd-stable Fri Jul 18 13:58:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA15609 for stable-outgoing; Fri, 18 Jul 1997 13:58:29 -0700 (PDT) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA15459; Fri, 18 Jul 1997 13:54:58 -0700 (PDT) Received: (from amir@localhost) by prozac.neuron.net (8.8.6/8.6.12) id QAA16387; Fri, 18 Jul 1997 16:54:26 -0400 (EDT) Message-ID: <19970718165426.63437@neuron.net> Date: Fri, 18 Jul 1997 16:54:26 -0400 From: "Amir Y. Rosenblatt" To: freebsd-stable@freebsd.org, freebsd-scsi@freebsd.org Subject: [2.2.2] Probelms with scsi tape and disk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I upgraded to 2.2.2-stable a couple weeks ago from 2.2.1 (via cvsup'ing the full source tree, and then doing the upgrade as per the instructions in the FreeBSD Manual) and since then I've not been able to write anything to my SCSI tape drive. I was able to do restores of dumped stuff but I can;t tar or dump to the tape now. I just attempted a tar and here's what came up in /var/log/messages: ----- Jul 18 16:45:22 prozac /kernel: sd0(ahc0:1:0): SCB 0x0 - timed out in dataout phase, SCSISIGI == 0x4 Jul 18 16:45:22 prozac /kernel: SEQADDR = 0x124 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 Jul 18 16:45:22 prozac /kernel: st0(ahc0:3:0): abort message in message buffer Jul 18 16:45:22 prozac /kernel: sd0(ahc0:1:0): SCB 0x3 timedout while recovery in progress Jul 18 16:45:22 prozac /kernel: st0(ahc0:3:0): SCB 2 - Abort Completed. Jul 18 16:45:22 prozac /kernel: st0(ahc0:3:0): no longer in timeout Jul 18 16:47:02 prozac /kernel: st0(ahc0:3:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Jul 18 16:47:02 prozac /kernel: SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Jul 18 16:47:02 prozac /kernel: st0(ahc0:3:0): SCB 2: Immediate reset. Flags = 0x1 Jul 18 16:47:02 prozac /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Jul 18 16:47:02 prozac /kernel: Clearing bus reset Jul 18 16:47:02 prozac /kernel: Clearing 'in-reset' flag Jul 18 16:47:02 prozac /kernel: st0(ahc0:3:0): no longer in timeout Jul 18 16:47:12 prozac /kernel: sd0(ahc0:1:0): UNIT ATTENTION asc:29,0 Jul 18 16:47:12 prozac /kernel: sd0(ahc0:1:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 Jul 18 16:47:12 prozac /kernel: , retries:4 ----- The machine's config is as follows: Tyan Dual PPro motherboard (with a single PPro200 on it) 96 meg of RAM Adaptec 2940UW SCSI host adapter Maxtor 4 gig IDE disk a pair of Seagate ST32550W Fast/Wise scsi disks HP SureStore 6000 tapedrive (I think it's the 6000 -- it's the 4 gig DDS-2 OEM internal DAT drive) 3Com 3c509B-TP ethernet card Number 9 "Imagine 128" 4 meg video card It should be noted that the tar that resulted in the above syslog spew was NOT being done from sd0 -- it was being done from wd0 (the IDE disk, which is currently serving as my boot disk). This has only started happening since the 2.2.2 upgrade. Any ideas? -Amir -- / \ Bite marks in the naugahide. | Amir Y. Rosenblatt /<@>\ - Red Meat | amir@neuron.net / \ FNORD | http://www.neuron.net/~amir _/_______\____________________________________|____________________________