Sun Storage A5000 Array
 
Solaris SPARC Operating System
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other
 

1. You run a 'boot -r' and the device links in /dev/dsk and
/dev/rdsk do not get created, even though the special files
do get created under the /devices directory.

2. Running the 'disks' or the 'luxadm' command gives a message in
the following format:

       Disk controller dsk/2 is linked to
../../devices/sbus@3,0/SUNW,fas@3,8800000 and
../../devices/sbus@6,0/SUNW,socal@d,10000/sf@0,0
Error: Could not run disks.

Note: Of course, the actual paths on your machine will be different.

All of the devices that have the same controller number (i.e., c1, c2, ...)
must be on the same physical device, and therefore, contain the same
physical path. In other words, it is illegal to have a device, say
c2t0d0, be on a SPARCstorage(R) Array, and another device with the same
controller number, say c2t6d0, be on an internal scsi controller.

However, this is exactly what causes this problem. If there are
existing entries in the /dev/dsk or /dev/rdsk directories that conflict
like this, the /usr/sbin/disks program produces an error and refuses
to create any new entries until YOU fix the conflict.

Here is an abbreviated example of an 'ls -l' of an afflicted /dev/dsk
directory:

1. ls -l /dev/dsk/*s2

lrwxrwxrwx 1 root root 74 Apr 20 1998 c2t0d0s2 ->
../../devices/sbus@6,0/SUNW,socal@d,10000/sf@0,0/ssd@w22000020370c5a91,0:c
lrwxrwxrwx 1 root root 74 Apr 20 1998 c2t18d0s2 ->
../../devices/sbus@6,0/SUNW,socal@d,10000/sf@0,0/ssd@w22000020370ca8d8,0:c
lrwxrwxrwx 1 root root 74 Apr 20 1998 c2t1d0s2 ->
../../devices/sbus@6,0/SUNW,socal@d,10000/sf@0,0/ssd@w22000020370cb964,0:c
lrwxrwxrwx 1 root root 74 Apr 20 1998 c2t20d0s2 ->
../../devices/sbus@6,0/SUNW,socal@d,10000/sf@0,0/ssd@w22000020370cb725,0:c
lrwxrwxrwx 1 root root 74 Aug 1 09:51 c2t22d0s2 ->
../../devices/sbus@6,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037131dfd,0:c
lrwxrwxrwx 1 root other 74 Apr 28 1998 c2t2d0s2 ->
../../devices/sbus@6,0/SUNW,socal@d,10000/sf@0,0/ssd@w22000020370d3ef7,0:c
lrwxrwxrwx 1 root root 74 Apr 20 1998 c2t3d0s2 ->
../../devices/sbus@6,0/SUNW,socal@d,10000/sf@0,0/ssd@w22000020370cbd32,0:c
lrwxrwxrwx 1 root root 74 Aug 1 09:51 c2t4d0s2 ->
../../devices/sbus@6,0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037131cf4,0:c
lrwxrwxrwx 1 root root 50 Sep 9 17:45 c2t6d0s2 ->
../../devices/sbus@3,0/SUNW,fas@3,8800000/sd@6,0:c

Notice how all the devices on c2 seem to be in a Sun StorEdge[TM] A5000,
except for c2t6d0, which is hanging off an internal SCSI bus. This is the
problem. Remove all the links that are "incorrect", for example:

       rm /dev/dsk/c2t6*

Then run the 'disks' command again to make sure no problems remain.
When the 'disks' command runs correctly, there should be no output.

Note:

In Solaris[TM] 2.5.1 Operating System and Solaris 2.6, the only way to add storage was to do a 'drvconfig;devlinks;disks'. In Solaris[TM] 8 and Solaris 7 with kernel patch 106541-08 and higher the devfsadm command replaces 'drvconfig;devlinks;xxxxx' and makes adding storage devices on the fly somewhat easier.

This solution has no attachment