Thanks to everyone who responded. Turns out I had one bad drive out of two
and one bad jumper out of two. Of course the bad jumper was on the good drive
and the good jumper on the bad one :-) I copied Dr. Blinn's response
because it was of great value to determine which drive was working and which
one wasnt.
Original question:
> > Im having trouble getting a DS10 running Tru64 4.0f to recognize two
> > new ultra2 18Gb disks. It has a ultra2 9.1Gb disk originally
> > installed. The disks came with no documentation and I havent been able
> > to find any online either. Im pretty sure the problem is with the SCSI
> > ID# but am not sure. The system has a scsi ultra2 cable where one end
> > is connected to the board and then the next slot in connected to the
> > original disk. The cable has the connectors for 3 more devices and then
> > what looks to be a terminator on the end.
> >
> > I connected the second connector to one disk and the third connector to
> > another disk. One disk came with a jumper which looked to be setting
> > the id to 1. Even when connected alone the system would not see the
> > disk. I tried doing a MAKEDEV in /dev but to no avail. It looks like
> > when the system is booting it sees the disks at scsi1 and scsi2. The
> > lights on the drives blink when booting but the system doesnt recognize
> > the drives. The original disk is seen at /dev/rz16.
> >
> > I have worked extensively with storageworks disks on an ES40 and a 2100A
> > but never with internal scsi disks as this. Any ideas of what I need to
> > do to get the system to see the disks would be appreciated.
> >
> > darryl
>
Response from Dr. Blinn
>
> >From whom did you buy the disks? I believe the internal SCSI adapter on
> the DS10 is either single ended or LVD capable (but you didn't say what
> is in the system and I don't know without doing research). If you have
> two single ended or LVD capable drives, the real issue is likely to be
> getting them jumpered to be at SCSI IDs (target addresses) that are NOT
> in conflict with your existing drive (which is drive zero on the bus).
>
> You can do most of this at the SRM console. Disconnect all three of
> the drives. Connect ONE of the new drives (either one) to the same
> place on the cable where your existing system disk was connected. Do
> an "init" in the console, then "show dev". If it does see the drive
> you will now know what address it's jumpered for. With V4.0x of UNIX,
> it MUST be in the range 0-6; the adapter is ID 7 and the V4.0F UNIX
> software can not deal with drives in the range 8-15. If the console
> doesn't see the drive, there is no way UNIX is going to see it. Once
> you get the first drive jumpered to be, say, drive 1, then fiddle with
> the second drive and get it jumpered to be, say, drive 2. Now try to
> get all three drives connected to the cable and visible to the console
> firmware. Again, you need to "init" after you swap drives around, and
> then "show dev". You do NOT have to power cycle the system while you
> are doing this, unless you are going to connect and disconnect drives
> from the power cables -- you could blow the power supply if you manage
> to get something grounded that should not be. But you can move SCSI
> cables around with the drives powered up and the system powered up and
> as long as you "init" the console will find the current configuration.
>
> Once you have all three drive visible IN THE CONSOLE with your existing
> system disk as drive 0 and the other two drives in the range 1-6, you
> can boot into your UNIX kernel and all the drives will be seen during
> the boot. If you CAN'T see the drives in the console, there is no way
> UNIX is going to see them, and if they are at "wide" IDs (8-15), they
> are not going to work, either.
>
> Tom
>
> Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation
> 110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698
> Technology Partnership Engineering Phone: (603) 884-0646
> Internet: tpb_at_zk3.dec.com - or - thomas.blinn_at_compaq.com
> ACM Member: tpblinn_at_acm.org PC_at_Home: tom_at_felines.mv.net
>
> Worry kills more people than work because more people worry than work.
>
> Keep your stick on the ice. -- Steve Smith ("Red Green")
>
> My favorite palindrome is: Satan, oscillate my metallic sonatas.
> -- Phil Agre, pagre_at_alpha.oac.ucla.edu
>
> Yesterday it worked / Today it is not working / UNIX is like that
> -- apologies to Margaret Segall
>
> Opinions expressed herein are my own, and do not necessarily represent
> those of my employer or anyone else, living or dead, real or imagined.
>
Received on Wed Jun 27 2001 - 18:09:42 NZST