Feico Dillema <feico@pasta.cs.uit.no> writes:
> scsibus0: waiting 2 seconds for devices to settle...
> siop0: target 0 using 16bit transfers
> siop0: target 0 now synchronous at 20.0Mhz, offset 15
> sd0 at scsibus0 target 0 lun 0: <IBM OEM, DCHS09U, 6363> SCSI2 0/direct fixed
> sd0: 8689 MB, 6082 cyl, 18 head, 162 sec, 512 bytes/sect x 17796077 sectors
> siop0: target 4 using 16bit transfers
> siop0: target 4 now synchronous at 20.0Mhz, offset 15
> scsibus0 target 4 lun 0: <IBM OEM, DCHS09U, 6363> SCSI2 0/direct fixed not configured

> Does this indicate a termination/cable problem of some kind or is
> somethign else wrong?

What does his configuration file look like?  One immediate guess
would be that it contains:
sd0   at scsibus? target ? lun ?
(or possibly even more wired down than that)
instead of
sd*   at scsibus? target ? lun ?

I suspect that this could cause the behavior you described.

					-jarle
-- 
"[P]ostulating that the VAX architecture would be missing any
 instruction `XYZ' is like playing Russian roulette with five
 bullets instead of one."  --  Dave McGuire on port-vax