From owner-freebsd-questions Wed May 21 23:23:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA04246 for questions-outgoing; Wed, 21 May 1997 23:23:20 -0700 (PDT) Received: from darius.concentric.net (darius.concentric.net [207.155.184.79]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA04241 for ; Wed, 21 May 1997 23:23:18 -0700 (PDT) Received: from newman.concentric.net (newman.concentric.net [207.155.184.71]) by darius.concentric.net (8.8.5/(97/05/21 3.30)) id CAA12343; Thu, 22 May 1997 02:23:14 -0400 (EDT) [1-800-745-2747 The Concentric Network] Received: from shag (ts002d08.sal-ut.concentric.net [206.173.156.44]) by newman.concentric.net (8.8.5) id CAA05285; Thu, 22 May 1997 02:23:08 -0400 (EDT) Message-ID: <3383E61F.6D0B4CB0@concentric.net> Date: Thu, 22 May 1997 00:22:23 -0600 From: Joshua Fielden Organization: Shaggy Enterprises X-Mailer: Mozilla 4.0b4 [en] (Win95; I) MIME-Version: 1.0 To: Stefan `Sec` Zehl CC: freebsd-questions@FreeBSD.ORG Subject: Re: strange 2.2.1 behavior X-Priority: 3 (Normal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stefan `Sec` Zehl wrote: > May 21 02:39:55 quit /kernel: (ncr0:1:0): "QUANTUM LPS540S 5900" type 0 fixed SCSI 2 > May 21 02:39:55 quit /kernel: sd0(ncr0:1:0): Direct-Access > May 21 02:39:55 quit /kernel: sd0(ncr0:1:0): 10.0 MB/s (100 ns, offset 8) > May 21 02:39:55 quit /kernel: 516MB (1057616 512 byte sectors) > May 21 02:39:55 quit /kernel: (ncr0:6:0): "QUANTUM FIREBALL_TM2110S 300X" type 0 fixed SCSI 2 > May 21 02:45:51 quit xntpd[89]: time reset (step) 0.232638 s > May 21 03:10:02 quit /kernel: sd0(ncr0:1:0): UNIT ATTENTION asc:29,0 > May 21 03:10:02 quit /kernel: sd0(ncr0:1:0): Power on, reset, or bus device reset occurred Sounds to me like the QUANTUM LPS540S 5900 drive is having problems or the chain is not set up right. I'm not totally familiar with the BSD system yet, is there any log that will show the sense data on the SCSI chain right before the errors? Have you double-checked termination, parity, and other jumper settings? -- SCSI is *not* magic. There are many technical reasons why it is occasionally nessicary to sacrifice a small goat to your SCSI chain. -- Joshua Fielden