Date: Thu, 22 May 1997 00:22:23 -0600 From: Joshua Fielden <shag@concentric.net> To: Stefan `Sec` Zehl <sec@42.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: strange 2.2.1 behavior Message-ID: <3383E61F.6D0B4CB0@concentric.net> References: <slrn5o5ks4.svk.sec@matrix.42.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Stefan `Sec` Zehl wrote:
<snip>
> 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
<snip>
> 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
<more of above>
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3383E61F.6D0B4CB0>