Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!bacchus.pa.dec.com!deccrl!decvax.dec.com!abyss.zk3.dec.com!tarsa From: tarsa@abyss.zk3.dec.com (Greg Tarsa) Newsgroups: comp.periphs.scsi Subject: Re: Drive not recognised by diag Message-ID: <345@decvax.decvax.dec.com.UUCP> Date: 21 Aug 90 15:13:09 GMT References: Sender: news@decvax.dec.com.UUCP Reply-To: tarsa@abyss.zk3.dec.com (Greg Tarsa) Distribution: comp Lines: 34 In article , 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