On Tue, Aug 07, 2001 at 06:24:04PM +0200, Rob Hoopman wrote:
> A while back Feico Dillema posted to this list about my siop prob, so I 
> thought I'd subscribe to the list myself again.
> 
> I am still getting strange errors from my siop card. 
> I did have my explicitly wired to device numbers, which I Ideally still want 
> to do because I am using raidframe and don't want my devices moving araound 
> in case of drive failures.
> Anyhow, the problem I am having at the moment (without the drives wired to 
> device numbers ): 
> 
> Is this just a cable length problem, or something else?
> 
> Rob
> 
> ======dmesg output========
> siop0: phase mismatch without command
> siop0: unhandled scsi interrupt, sist=0x90 sstat1=0xf DSA=0xffffffff DSP=0xa0
> siop0: scsi bus reset
> cmd 0xc0746080 (target 0:0) in reset list
> cmd 0xc07462c0 (target 2:0) in reset list
> cmd 0xc0746080 (status 2) about to be processed
> cmd 0xc07462c0 (status 2) about to be processed
> siop0: target 0 now synchronous at 20.0Mhz, offset 15
> raid0: node (R  ) returned fail, rolling backward
> raid0: DAG failure: r addr 0x669140 (6721856) nblk 0xc (12) buf 0xcbe27000
> siop0: target 1 now synchronous at 20.0Mhz, offset 15
> siop0: target 6 asynchronous
> sd0(siop0:0:0): scsi gross error
> siop0: scsi bus reset
> cmd 0xc0746040 (target 0:0) in reset list
> cmd 0xc0746040 (status 2) about to be processed
> siop0: target 0 now synchronous at 20.0Mhz, offset 15
> sd0: ..is spinning up...waiting
> siop0: target 1 now synchronous at 20.0Mhz, offset 15
> siop0: target 2 now synchronous at 20.0Mhz, offset 15
> siop0: target 6 asynchronous
> sd0(siop0:0:0): command timeout
> siop0: scsi bus reset
> cmd 0xc0746240 (target 0:0) in reset list
> cmd 0xc0746240 (status 2) about to be processed
> siop0: target 0 now synchronous at 20.0Mhz, offset 15
> sd0: ..is spinning up...waiting

Hum, I would say sd0 has serious problems. Why did it spin down ?
Usually a HD spinning down while in use is dying.

--
Manuel Bouyer <bouyer@antioche.eu.org>
--