From owner-freebsd-scsi Mon Jan 6 08:17:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA13987 for freebsd-scsi-outgoing; Mon, 6 Jan 1997 08:17:16 -0800 (PST) Received: from gatekeeper.fsl.noaa.gov (gatekeeper.fsl.noaa.gov [137.75.131.181]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA13982 for ; Mon, 6 Jan 1997 08:17:13 -0800 (PST) Received: from cardinal.fsl.noaa.gov (daemon@cardinal.fsl.noaa.gov [137.75.60.101]) by gatekeeper.fsl.noaa.gov (8.7.5/8.7.3) with ESMTP id QAA00443 for ; Mon, 6 Jan 1997 16:17:12 GMT Received: from auk.fsl.noaa.gov by cardinal.fsl.noaa.gov with SMTP (1.40.112.3/16.2) id AA261597432; Mon, 6 Jan 1997 16:17:12 GMT Message-Id: <32D125EB.4E3F@fsl.noaa.gov> Date: Mon, 06 Jan 1997 09:18:51 -0700 From: Kelly Organization: CIRA/NOAA X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.10 9000/725) Mime-Version: 1.0 To: scsi@freebsd.org Subject: Problem appears from migration from bt0 to ncr0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello SCSI experts. I've recently migrated a host using a Buslogic 946C to an NCR 53C810. This machine contains a DAT drive and I use it as an Amanda dumphost. It also contains a DFRS hard drive. That's where the problem is. The DFRS is a good capacity drive that's nice 'n fast and doesn't even run too hot, but it goes asleep ever so often for some kind of thermal calibration period or something. During this time, the Buslogic driver would report "bt0: try to abort" but everything would be fine afterward. Now, with the NCR driver, things get confused. The thermal calibration period will cause syslogd to have an input/output error trying to write messages to disk. The kernel spits out ncr0: restart (ncr dead ?). Jan 6 03:47:07 sage /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Jan 6 03:47:07 sage /kernel: sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 Jan 6 03:47:07 sage /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred Now, although alarming, the filesystems seem OK. The disk works afterwards as does the CD-ROM. But the worse part is this: access to any sequential devices on the SCSI bus stops working. Any tape activity results in input/output error and messages like the following: Jan 6 06:57:22 sage /kernel: st1(ncr0:3:0): 275ns (4 Mb/sec) offset 8. Jan 6 06:57:22 sage /kernel: st1(ncr0:3:0): NOT READY asc:4,1 Jan 6 06:57:22 sage /kernel: st1(ncr0:3:0): Logical unit is in process of becoming ready Jan 6 06:57:37 sage /kernel: ncr0: restart (ncr dead ?). It looks like any tape activity causes a bus reset, and the tape drives can't handle it. But I'm probably wrong. Now, I wouldn't mind chucking the DFRS drive into the nearest active volcano complete with massive cinder dome and flying sparks and other nifty special effects, but my wife would frown on more computer equipment appearing on the credit card bill. So, is there anything you could recommend I try in software? -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/