This is happening here too, I have RZ56 disks and they report the same.

The disks does not spin up when kernel scans the disks, I asked some
weeks ago and got little answers. I can use the disks with freebsd if I
issue START_UNIT command prior to mount them. The disks does not listen
to SPIN_UP command from adaptec controller, but only from START_UNIT
command in scsi CAM interface of freebsd.

My disks did also work with VMS.

I remember that the start sequence was litle bit funny with vms, started
to boot from RZ24 and when the system was nearly fully up, the two RZ56
disks was started one by one and mounted.


In camcontrol man page from freebsd is start unit command 0x1b with
start bit set ???
0x1b has start/stop bit, eject bit and ...

Þórður Ívarsson


Peter Garay wrote:
> 
> On Tue, 15 Feb 2000, Gyenes Istvan wrote :
> > ncr1: no REQ for next phase, abort
> > ncr1: no REQ while aborting, reset
> > ncr1: reset SCSI bus for TID=3 LUN=0
> > ncr1: no REQ for next phase, abort
> > ncr1: no REQ while aborting, reset
> > ncr1: reset SCSI bus for TID=3 LUN=0
> > ncr1: no REQ for next phase, abort
> >
> Istvan,
> 
> I leave these messages to analyse who have spent some time with this, and do
> not have this drive either. The first question is if the drive is accessable by
> any other OS (vms, ultrix) ? Cable problems also may allow the console to find
> the device, but fail when read/write commands are issued.
> 
> Rgds,
> 
> P.G.
> 
> ps:
> Elnezest a kivancsisagert, sch a villamos kari kollegium a szep kek
> toronyhazban?