SCSI ID/target for new hard disk

[Vicki Rosenzweig]

I have an old Sparc IPX box running SunOS 4.1.3U1. I
want to attach a 9-gigabyte Seagate ST39173N hard disk
to this system. We already have an internal disk and
two external hard disks in the SCSI chain. The existing
disks are sd0 (boot) at SCSI target 3; sd1 at SCSI
target 1; and sd2 at SCSI target 2.

When I set the new disk to be sd3, the system can't
see it at all. When I set it to be sd4, it's visible
to probe-scsi, but not to format.

It looks as though what I want is for the new disk to be
sd3 at target 0. The kernel I'm running--not much modified
from GENERIC--supports this. Can anyone point me at what
else I need to do to accomplish this?

Alternatively, would anything horrible happen if I rebuilt
the kernel to put this at target 4 or 5, since there are
no tape drives attached to this system?

Thank you for any help.

--
Don't mourn--organize
Vicki Rosenzweig
v...@redbird.org | http://www.panix.com/~vr/

Sent via Deja.com
http://www.deja.com/

[C. Newport]

Vicki Rosenzweig wrote:
>
> I have an old Sparc IPX box running SunOS 4.1.3U1. I
> want to attach a 9-gigabyte Seagate ST39173N hard disk
> to this system. We already have an internal disk and
> two external hard disks in the SCSI chain. The existing
> disks are sd0 (boot) at SCSI target 3; sd1 at SCSI
> target 1; and sd2 at SCSI target 2.
>
> When I set the new disk to be sd3, the system can't
> see it at all. When I set it to be sd4, it's visible
> to probe-scsi, but not to format.
>
> It looks as though what I want is for the new disk to be
> sd3 at target 0. The kernel I'm running--not much modified
> from GENERIC--supports this. Can anyone point me at what
> else I need to do to accomplish this?
>
> Alternatively, would anything horrible happen if I rebuilt
> the kernel to put this at target 4 or 5, since there are
> no tape drives attached to this system?

4.1.3 is just not designed to use large drives, but here's how
I did it using 4.1.4 and it MIGHT work for you.

First you need to set up the parameters for the disk.
There is a disk parameter list which is posted here regularly,
or you can cheat by formatting and labelling the disk on a
Solaris 2.6 machine. (7 or 8 MIGHT be OK)

Your boot slice MUST be 1G or less, all other slices must be
2G or less.

Now take the drive back to your own machine and newfs each slice.
It is important to note that 4.1.x cannot recognise the upgraded
ufs filesystem used by Solaris 2.x.

It really is about time you upgraded your OS, I would suggest
Solaris 2.6 on an IPX, it will run in 16Mb but your really
need 32Mb or more. If you can cram in 64Mb you could use Solaris 7.
Solaris 8 will not run.