[comp.periphs.scsi] Drive not recognised by diag

evan@cs.mu.OZ.AU (Evan Harris) (08/21/90)

We are attempting to install a new Micropolis 1588-15 SCSI drive with
a Sun 3/60 running SunOS 3.5 via an Emulex MD21 controller.  The
controller already has a SCSI disk and tape drive attached.

The new drive is set to be SCSI unit 1, the Emulex unaltered, however
diag cannot find the new drive, instead producing:

ncycl 1614 acyl 2 nhead 15 nsect 54 interleave 1
reset the SCSI bus...
Test unit ready failed, cyl=0, head=0, sector=0 scb: 2 check
sense bytes: 70 0 2 0 0 0 0 A 0 0 0 0 FF
sense class 7
	sense key 2 Not Ready.
	block no. 0

It still works fine for unit 0, and the drive is ok.

Have we missed something obvious?  Thanks in advance for any
information.

 -------------------------------8<-------------------------------
 Evan Harris
 evan@goanna.cs.rmit.OZ.AU              Dept. of Computer Science
 ...!uunet!goanna.cs.rmit.OZ.AU!evan         RMIT, Australia

tarsa@abyss.zk3.dec.com (Greg Tarsa) (08/21/90)

In article <EVAN.90Aug21184128@murgon.cs.mu.OZ.AU>, evan@cs.mu.OZ.AU
(Evan Harris) writes:
|> We are attempting to install a new Micropolis 1588-15 SCSI drive with
|> a Sun 3/60 running SunOS 3.5 via an Emulex MD21 controller.  The
|> controller already has a SCSI disk and tape drive attached.
|> 
|> The new drive is set to be SCSI unit 1, the Emulex unaltered, however
|> diag cannot find the new drive, instead producing:
|> 
It is not clear to me from your description how your disk/controller
hardware is set up.  If the original diak/tape/controllers work and are
in a shoebox and your new disk has its own controller is (perhaps) is in
another shoebox, then your problem may be that the second MD21 needs to be
set to be SCSI target #1 (not #0, which is how the target adaptor in your
original shoebox is probably set) and you will have to tell diag to
look at target #1, disk #1.  In fact, if this *is* your situation, then
you can set the disk to be unit #0 and tell diag to look at target #1, disk #0.

Also note, when it comes time to configure the new disk into the kernel,
you will have to have describe the device as having a drive number of 9,
which is the target number (1) times 8 plus the disk unit number (1).

Something like the following:
	disk sd1 at sc0 drive 9 flags x

Hope this helps,
Greg

 
Tarsa Software Consulting
--------------------------------
		33 Seabee Street
		Bedford, NH 03102	tarsa@elijah.mv.com
		(603)668-9226		{decuac,decvax}!elijah!tarsa

evan@cs.mu.OZ.AU (Evan Harris) (08/22/90)

>>>>> On 21 Aug 90 15:13:09 GMT, tarsa@abyss.zk3.dec.com (Greg Tarsa) said:

In article <EVAN.90Aug21184128@murgon.cs.mu.OZ.AU>, evan@cs.mu.OZ.AU
(Evan Harris) writes:
|> We are attempting to install a new Micropolis 1588-15 SCSI drive with
|> a Sun 3/60 running SunOS 3.5 via an Emulex MD21 controller.  The
|> controller already has a SCSI disk and tape drive attached.
|> 
|> The new drive is set to be SCSI unit 1, the Emulex unaltered, however
|> diag cannot find the new drive, instead producing:
|> 

Greg> It is not clear to me from your description how your
Greg> disk/controller hardware is set up.  If the original
Greg> diak/tape/controllers work and are in a shoebox and your new

Yes.

Greg> disk has its own controller is (perhaps) is in another shoebox,

No, the new disk does not have its own controller.  We want it to be
unit #1 on the existing MD21.  I assume this is possible?

 -------------------------------8<-------------------------------
 Evan Harris
 evan@goanna.cs.rmit.OZ.AU              Dept. of Computer Science
 ...!uunet!goanna.cs.rmit.OZ.AU!evan         RMIT, Australia