Very Computer

Hello,

I'm having problem replacing a SCSI disk on my sun SparcServer 1000E.
I have an old (NARROW) micropolis 2.1 Gb drive that is giving me
errors in the /var/adm/messages.  I wanted to replace it with a new
barracuda 9Gb drive that I configured to use the same SCSI ID as the
old disk.

I removed the mount entry for the drive to be rewplaced from
/etc/vfstab, shut the server down, turned off all peripherals and
proceeded to replace the micropolis drive with the new drive, this
required a change of cables (See figure below)

Old setup:

Sun N---------C
             -C  Micropolis drive
            |
             -C  Other drives
             -C
             |_...T

New setup:

Sun N---------W
             -W Barracuda
            |
             -C  Other drives
             -C
             |_...T

- = Cable
W = Wide SCSI connector
N = Narrow SCSI connector (Not centronics type)
C = Narrow, "centronics" type connector.

The lenght of the SCSI chain did not increase, actually it probably
decreased.  The barracuda is NOT TERMINATED, I removed the appropriate
jumper (I tested it on an NT machine and it was seen as ID 4 correctly
and was functionnal)

What happens when I boot is that no devices are recognized anymore on
the SCSI chain where a drive was replaced.

What might be the problem here ?

a) Terminator issues (The barracuda had a terminator jumper that I
removed, but there are two other jumpers that say:

       - Drive supplies Bus termination power
       - Drive supplies own termination power (Default)
       - Bus supplies drive termination power

b) N,W,C connector mixing causing problems ? We have a similar setup
on another chain and it runs fine

c) Should I touch /reconfigure even if I'm not adding a new drive but
REPLACING an existing drive with a different drive ? I don't thinks so
because at the prom prompt, the probe-scsi-all gave errors on that
particular bus as well.

d) Cable problem ? On of the cables is new

Any suggestions, hints would be appreciated.

Thanks

NOTE: To reply via e-mail, remove the 'anti-spam-' from my e-mail adress

Please see my previous problem.

The external enclosure I used to put the 9gb barracuda drive has two
SCSI connectors. On the manuals, they say one is SCSI in and the other
SCSI out, does it really matter which connector I plug the cable on or
should I enter by the SCSI IN and exit by the out toward the end of
the SCSI chain ?

NOTE: To reply via e-mail, remove the 'anti-spam-' from my e-mail adress

Quote:>Hello,

>I'm having problem replacing a SCSI disk on my sun SparcServer 1000E.
>I have an old (NARROW) micropolis 2.1 Gb drive that is giving me
>errors in the /var/adm/messages.  I wanted to replace it with a new
>barracuda 9Gb drive that I configured to use the same SCSI ID as the
>old disk.

>I removed the mount entry for the drive to be rewplaced from
>/etc/vfstab, shut the server down, turned off all peripherals and
>proceeded to replace the micropolis drive with the new drive, this
>required a change of cables (See figure below)

>Old setup:

>Sun N---------C
>             -C  Micropolis drive
>            |
>             -C  Other drives
>             -C
>             |_...T

>New setup:

>Sun N---------W
>             -W Barracuda
>            |
>             -C  Other drives
>             -C
>             |_...T

>- = Cable
>W = Wide SCSI connector
>N = Narrow SCSI connector (Not centronics type)
>C = Narrow, "centronics" type connector.

>The lenght of the SCSI chain did not increase, actually it probably
>decreased.  The barracuda is NOT TERMINATED, I removed the appropriate
>jumper (I tested it on an NT machine and it was seen as ID 4 correctly
>and was functionnal)

>What happens when I boot is that no devices are recognized anymore on
>the SCSI chain where a drive was replaced.

>What might be the problem here ?

>a) Terminator issues (The barracuda had a terminator jumper that I
>removed, but there are two other jumpers that say:

>       - Drive supplies Bus termination power
>       - Drive supplies own termination power (Default)
>       - Bus supplies drive termination power

>b) N,W,C connector mixing causing problems ? We have a similar setup
>on another chain and it runs fine

>c) Should I touch /reconfigure even if I'm not adding a new drive but
>REPLACING an existing drive with a different drive ? I don't thinks so
>because at the prom prompt, the probe-scsi-all gave errors on that
>particular bus as well.

>d) Cable problem ? On of the cables is new

>Any suggestions, hints would be appreciated.

>Thanks

>NOTE: To reply via e-mail, remove the 'anti-spam-' from my e-mail adress

Please see my previous problem.

The external enclosure I used to put the 9gb barracuda drive has two
SCSI connectors. On the manuals, they say one is SCSI in and the other
SCSI out, does it really matter which connector I plug the cable on or
should I enter by the SCSI IN and exit by the out toward the end of
the SCSI chain ?

NOTE: To reply via e-mail, remove the 'anti-spam-' from my e-mail adress

Sorry, I can't see your previous at the moment, but it does matter for
devices
that have suto-termination, particularly if narrow and wide devices are
being mixed.  Suggest that you stick with manufacturer's recommendations,
and
try to avoid situations where narrow and wide devices are mixed on a single
bus.
Some claim to have made it work by putting the narrow device at the end of
the
line, but I've never tried it myself

Speaking only for myself,

Joe Durusau

Quote:> Please see my previous problem.

> The external enclosure I used to put the 9gb barracuda drive has two
> SCSI connectors. On the manuals, they say one is SCSI in and the other
> SCSI out, does it really matter which connector I plug the cable on or
> should I enter by the SCSI IN and exit by the out toward the end of
> the SCSI chain ?

> NOTE: To reply via e-mail, remove the 'anti-spam-' from my e-mail adress

Quote:> Please see my previous problem.

> The external enclosure I used to put the 9gb barracuda drive has two
> SCSI connectors. On the manuals, they say one is SCSI in and the other
> SCSI out, does it really matter which connector I plug the cable on or
> should I enter by the SCSI IN and exit by the out toward the end of
> the SCSI chain ?

I'm not sure.  I make the "IN" the side nearer the computer.
The install documents which come with drives using these enclosures
have figures like this:

[computer] <----scsi---->[IN    OUT] <<+++++no terminator needed here

showing that if the device is at the end of the chain, the OUT side
doesn't need to be terminated, and this indeed works.

Best wishes,
  Mike

Quote:> Hello,

> I'm having problem replacing a SCSI disk on my sun SparcServer 1000E.
> I have an old (NARROW) micropolis 2.1 Gb drive that is giving me
> errors in the /var/adm/messages.  I wanted to replace it with a new
> barracuda 9Gb drive that I configured to use the same SCSI ID as the
> old disk.

> I removed the mount entry for the drive to be rewplaced from
> /etc/vfstab, shut the server down, turned off all peripherals and
> proceeded to replace the micropolis drive with the new drive, this
> required a change of cables (See figure below)

> Old setup:

> Sun N---------C
>              -C  Micropolis drive
>             |
>              -C  Other drives
>              -C
>              |_...T

> New setup:

> Sun N---------W
>              -W Barracuda
>             |
>              -C  Other drives
>              -C
>              |_...T

> - = Cable
> W = Wide SCSI connector
> N = Narrow SCSI connector (Not centronics type)
> C = Narrow, "centronics" type connector.

> The lenght of the SCSI chain did not increase, actually it probably
> decreased.  The barracuda is NOT TERMINATED, I removed the appropriate
> jumper (I tested it on an NT machine and it was seen as ID 4 correctly
> and was functionnal)

> What happens when I boot is that no devices are recognized anymore on
> the SCSI chain where a drive was replaced.

> What might be the problem here ?

> a) Terminator issues (The barracuda had a terminator jumper that I
> removed, but there are two other jumpers that say:

>        - Drive supplies Bus termination power
>        - Drive supplies own termination power (Default)
>        - Bus supplies drive termination power

> b) N,W,C connector mixing causing problems ? We have a similar setup
> on another chain and it runs fine

> c) Should I touch /reconfigure even if I'm not adding a new drive but
> REPLACING an existing drive with a different drive ? I don't thinks so
> because at the prom prompt, the probe-scsi-all gave errors on that
> particular bus as well.

> d) Cable problem ? On of the cables is new

> Any suggestions, hints would be appreciated.

> Thanks

> NOTE: To reply via e-mail, remove the 'anti-spam-' from my e-mail adress

Anytime you change any kind of hardware configuration I would do a
reconfigure boot
(i.e. ok> boot -r OR # touch/reconfigure;reboot     - they do the same
thing)

I would try booting up with only the 9GB drive on the SCSI chain to make
sure it is
recognized ok. Then if it is, I would add one device on the chain at a time
(rebooting each
time.)

Did you switch to a Wide SCSI controller (68-pin mini) or are you using a
Fast SCSI-2
controller (50-pin mini/Narrow)? I'm not sure if a Fast SCSI-2 controller
can handle
wide SCSI devices, but a wide SCSI controller CAN handle narrow SCSI
devices.

Hope this helps.