SUMMARY: Adding DiskPack on SS10 and Solaris 2.2

From: Anil Katakam +1 201 386 2524 (fuwutai!katkam)
Date: Sat Oct 02 1993 - 07:48:02 CDT

Anyway the unanimous answer was to
 1. boot -r from prom level
 2. reboot -- -r from command line or
 3. touch /reconfigure and reboot

I guess the question was Dumb enough, since the answer seemed much too simple.
I'm in the process of getting used to this Solaris 2.x and am no SYSV guy.
I wish Sun had that one big binder things as in the past where I could refer
to in one place. It made life too complicated by having small books with as
little as 20 pages.

Thanks to all of you.

Anil Katakam :-)
>> |
>> | Managers,
>> | I have Installed a Sun 4.2 GB DiskPak on our SS10 running Solaris 2.2.
>> | We have added an FSBE/Sbus card and the DiskPAK was installed on this
>> | bus since there is already an internal drive sd0 in the system.
>> | The system upon reboot identifies the disk as sd7,8,9,10 on esp1. This
>> | I found from the "prtconf" command.
>> | However when I run format none of these drives are seen except for the
>> | root drive sd0 ( i.e. c0t3d0 ). I checked the /dev/rdsk dir for the
>> | device files for these disks. Since they were not there, I assume format
>> | does not know the new disks.
>> |
>> | My question is How do I make these new device files ( probably the equivalent
>> | of MAKEDEV in old SunOS ) ???.
>> |
>> | I looked through different Docs but couldn't find any info. Even the DiskPAK
>> | installation manual does not specify about it nor does the "Adding and Maintaining
>> | Devices and Device Drivers". Of course I refered to others too.
>> |
>> | If any of you have done this on a SS10 before please correct me if I did anything
>> | wrong. Since the DiskPAK installation manual did not tell me to change any jumpers
>> | nor does the FSBE/SCSI card if it needs to be the 2nd card on board. I didn't
>> | change any jumper settings.
>> |
>> |
From: :
         Just your basic dumb question - Did you do a boot -r to reconfigure
 the system? I just installed one on a Sparc1000 and all I had to do was
 plug it in, boot -r, format/partition and off it went!
 From: : Wayne Tilford
 The thing to do for Solaris is to :
 1. boot -r from prom level
 2. reboot -- -r from command line
 3. touch /reconfigure and reboot
 You would use prtconf to look for devices. The drvconfig utility is responsible
 for configuring the /devices directory to reflect the dev_info tree in the
 kernel. This utility is run automatically bu /sbin/rcS script.
 From: George Ross <>
 Did you remember to "boot -r" after you added the new hardware?
 From: (Endre Polgar)
 Use 'boot -r' to force the system to look for
 your new devices.

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:20 CDT