From owner-freebsd-scsi Wed Oct 8 02:38:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA07126 for freebsd-scsi-outgoing; Wed, 8 Oct 1997 02:38:27 -0700 (PDT) (envelope-from owner-freebsd-scsi) Received: from firewall.ftf.dk (root@mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA07117 for ; Wed, 8 Oct 1997 02:38:24 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id MAA32565 for ; Wed, 8 Oct 1997 12:09:19 +0200 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id LAA25828 for ; Wed, 8 Oct 1997 11:50:52 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.5/8.8.5/prosa-1.1) id LAA10464; Wed, 8 Oct 1997 11:37:25 +0200 (CEST) Message-ID: <19971008113725.46245@deepo.prosa.dk> Date: Wed, 8 Oct 1997 11:37:25 +0200 From: Philippe Regnauld To: freebsd-scsi@freebsd.org Subject: 2.2.2 anc NCR875 failures Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: Main Body X-Mailer: Mutt 0.69 X-Operating-System: FreeBSD 2.2.1-RELEASE i386 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just got (a week ago) a new machine to run a keyserver on... The configuration is TX97/K6-180, NCR-875, 64MB RAM, 2 x 2.2 Atlas II UW disks. I've had the following failure three times so far, I would guess during some fair amount of disk i/o: (written on paper, I'm trying to reread myself): ncr0: ERROR (81:0) 8af80 (10/1b) @24:00000000 script cms = 98000000 reg = da 10 c0 1b 47 10 01 07 75 08 81 af 80 00 07 00 ncr0: restart (fatal error) ncr0:1: error 81:0 8af80 sd1:(ncr0:1:0) COMMAND FAILED (9ff) @ f0cf7e00 sd0:(ncr0:0:0) COMMAND FAILED (9ff) @ f0cf7e00 sd0:(ncr0:0:0) COMMAND FAILED (9ff) @ f0cd1800 [...] ncr0: timeout ccb = f0cf7e00 ncr0: timeout ccb = f0cf7600 ... In the two other cases, I had some other message, every 30 sec. or so, like "retrying block = xxxyyy". No crash, no reboot... I had to go and manually reset the machine (off-site!) every time. I tried reducing TAG number in ncrcontrol -- nada. Help ? PS: I'm not subscribed to the list, but will if necessary :-) -- -- Phil -[ Philippe Regnauld / Systems Administrator / regnauld@deepo.prosa.dk ]- -[ Location.: +55.4N +11.3E PGP Key: finger regnauld@hotel.prosa.dk ]-