[comp.sys.next] SCSI problem

kls30@duts.ccc.amdahl.com (Kent L Shephard) (02/21/91)

Well here's the deal.  I connected a Wren III to my cube internally and
the cube doesn't even see the disk.

I boot the machine running all the diagnostics and I get error code #65
which is a SCSI error.  I try to use builddisk and I get the message that
it can't find the device.   I tried an external drive and the same thing
happened.

Always the same thing scsimodes can't find the device.

If I have the Wren internally I get  ec #65 but if I have a Quantum I
don't get the error code on boot.

Just for the hell of it while in the ROM monitor I tried the command
bsd - to boot from the SCSI device to see what would happen.  It came
back with the message that the SCSI bus was hung.  The exact same thing
happens when there is no drive connected.

For the record I'm using a NeXT 50 pin SCSI cable internally and a generic
SCSI cable externally.

All this happens no matter what I have the device as (0-7).  I know that
#7 is reserved for the mother board but I tried this just to see if I could
get a conflict on the bus - nothing.

Help!!!  Help!!!   Help!!!  Help!!!  I NEED HELP!!!!!!!!!!

                         KeNT
--
/*  -The opinions expressed are my own, not my employers.    */
/*      For I can only express my own opinions.              */
/*                                                           */
/*   Kent L. Shephard  : email - kls30@DUTS.ccc.amdahl.com   */

jlc2@cbnewse.att.com (john.chmielewski) (02/22/91)

kls30@duts.ccc.amdahl.com (Kent L Shephard) writes:

>Well here's the deal.  I connected a Wren III to my cube internally and
>the cube doesn't even see the disk.

>[stuff deleted]

>Just for the hell of it while in the ROM monitor I tried the command
>bsd - to boot from the SCSI device to see what would happen.  It came
>back with the message that the SCSI bus was hung.  The exact same thing
>happens when there is no drive connected.

I've seen the same kind of problem when a Wren 4 was first attached to
the cube.  The problem was that the 50 pin SCSI flat ribbon cable was
connected upside down.  You should check to make sure that you do not
have the same problem.  When you look at a Wren 4 drive from the rear
(power connector on the right), pin 1 of the SCSI connector is on the
right.  I believe the same is also true for the Wren 3, however, if
you don't have a copy of the drive specs, you can download a copy,
including pinouts, from:
	SEAGATE TECHNOLOGY, INC.
	Technical Support Bulletin Board
	408/438-8771  [300-9600 HST, MNP 3/5, N-8-1]

Hope this helps.

	     			-jlc-
			jlc@alien.att.com

jchin@wimsey.bc.ca (Joseph Chin) (04/23/91)

Several weeks ago, I asked for information on SCSI problems people have
come across in hooking SCSI devices to their NeXT computers. I have
received many responses. I am sorting those those replies now, and I am
also waiting to hear from several other sources I've corresponded with.
I will put up a summary as soon as I can get all the information together.

Thank you very much to all those who replied. If anyone has any more
experiences with SCSI problems, please continue to e-mail me and let
me know of the details.

:-) Joe
jchin@van-bc.wimsey.bc.ca

-- 
 **************************************************************
 * "Kill the body and the head will die" (Hunter S. Thompson) *
 *    NeXT --> The ultimate electronic publishing platform!   *
 ********** Joseph Chin --> jchin@van-bc.wimsey.bc.ca *********