The second internal disk bay in my Ultra 2 has been empty for
5 years. I finally got a 36 GB SCA disk to fill it. I set
the jumper for SCSI target 4, which was not used by any other
device. When the machine booted, the new disk was seen at
address 5! What's going on?

By the way, I know I didn't accidentally jumper address 5,
because I only put on one jumper block.

--
* Patrick L. Nolan *
* W. W. Hansen Experimental Physics Laboratory (HEPL) *
* Stanford University *

On Fri, 09 Jul 2004 23:45:20 +0000, Patrick L. Nolan wrote:

> The second internal disk bay in my Ultra 2 has been empty for
> 5 years. I finally got a 36 GB SCA disk to fill it. I set
> the jumper for SCSI target 4, which was not used by any other
> device. When the machine booted, the new disk was seen at
> address 5! What's going on?

1+4=5

The backplane sets the target address to 1.

On Fri, 9 Jul 2004, Dave Uhring wrote:

> On Fri, 09 Jul 2004 23:45:20 +0000, Patrick L. Nolan wrote:
>
> > The second internal disk bay in my Ultra 2 has been empty for
> > 5 years. I finally got a 36 GB SCA disk to fill it. I set
> > the jumper for SCSI target 4, which was not used by any other
> > device. When the machine booted, the new disk was seen at
> > address 5! What's going on?
>
> 1+4=5
>
> The backplane sets the target address to 1.

Just to amplify that a bit: internal disks in Ultra 2s (and
many other Sun machines for that matter) should not have any
of the device ID jumpers set, because the backplane determines
the target ID.

--
Rich Teer, SCNA, SCSA

President,
Rite Online Inc.

Voice: +1 (250) 979-1638
URL: http://www.rite-online.net

Patrick L. Nolan wrote:
> The second internal disk bay in my Ultra 2 has been empty for
> 5 years. I finally got a 36 GB SCA disk to fill it.

Did you have to set a jumper to force single-ended mode?

Donn Miller <dmmiller@cvzoom.net> wrote:
> Patrick L. Nolan wrote:
>> The second internal disk bay in my Ultra 2 has been empty for
>> 5 years. I finally got a 36 GB SCA disk to fill it.

> Did you have to set a jumper to force single-ended mode?
No. Is that relevant? It's supposed to look at its inputs
and go single-ended on its own. It is working properly, so
it must have done so.
--
* Patrick L. Nolan *
* W. W. Hansen Experimental Physics Laboratory (HEPL) *
* Stanford University *

On Sun, 11 Jul 2004 04:08:21 +0000, Patrick L. Nolan wrote:
> Donn Miller <dmmiller@cvzoom.net> wrote:
[snippage]
>> Did you have to set a jumper to force single-ended mode?
> No. Is that relevant? It's supposed to look at its inputs
> and go single-ended on its own. It is working properly, so
> it must have done so.

Yes, most LVD drives "fall back" to SE automagically. I think there were
some early models that needed to be "forced", hence the jumper (if any).

--
Juhan Leemet
Logicognosis, Inc.

Juhan Leemet wrote:
> On Sun, 11 Jul 2004 04:08:21 +0000, Patrick L. Nolan wrote:
>
>>Donn Miller <dmmiller@cvzoom.net> wrote:
>
> [snippage]
>
>>>Did you have to set a jumper to force single-ended mode?
>>
>>No. Is that relevant? It's supposed to look at its inputs
>>and go single-ended on its own. It is working properly, so
>>it must have done so.
>
>
> Yes, most LVD drives "fall back" to SE automagically. I think there were
> some early models that needed to be "forced", hence the jumper (if any).
>

As I posted earlier, I've got a Seagate ST39173WC that is not getting
detected in my Ultra-2. I'm SOL, though, as there are no jumpers to
force SE.