How to determine the correct 'forceload' entries to use for a disk array.

Asset ID:	1-71-1004459.1
Update Date:	2012-05-16
Keywords:

Solution Type Technical Instruction Sure

Solution 1004459.1 : How to determine the correct 'forceload' entries to use for a disk array.

Related Items


Sun SPARCstorage Array

Related Categories


PLA-Support>Sun Systems>DISK>Arrays>SN-DK: A5xxx
 .Old GCS Categories>Sun Microsystems>Operating Systems>Solaris Operating System

PreviouslyPublishedAs
206155

Description
This article addresses how to determine the correct 'forceload' entries to use for a disk array.

Steps to Follow
Say you want to forceload all the necessary drivers for the disk array
you have attached to your system. How do you tell what "forceload"
statements to put into the /etc/system file?

First, do an 'ls -l' of one of the disks in the array.  For example,
# ls -l /dev/rdsk/c2t0d0s2
lrwxrwxrwx   1 root     root          74 Feb 23 09:58 /dev/rdsk/c2t0d0s2 -> ../../devices/sbus@3,0/SUNW,socal@2,0/sf@1,0/ssd@w22000020370f448d,0:c,raw
This is a symbolic link to the actual device file under the '/devices'
directory.  Each driver name is located after each slash ("/") and
before each 'at sign' ("@").  So for the above example, the drivers to
forceload would be "sbus", "SUNW,socal", "sf", and "ssd".
Therefore, the resulting "forceload" statements to put into the
/etc/system file would be:
forceload: drv/sbus
forceload: drv/SUNW,socal
forceload: drv/sf
forceload: drv/ssd

Product
Solaris

Previously Published As
18631

Change History
Article is missing a keyword statement, and the product statement needs to be a list of specific Solaris versions (eg: Solaris 8 Operating System).

MIGRATION CLEANUP
Product_uuid
3285bfa4-224e-11d6-8eb3-843d3a923213|Solaris

Attachments

This solution has no attachment