A specific procedure must be used when replacing one of the internal disks in a system with internal fibre drives

(280R, V480, V880) especially if the disk is under Veritas Volume Manager (VxVM) control. Failure to follow this procedure could result in a duplicate entry for the replaced disk in VxVM. This is most notable when running a 'vxdisk list'. For example: # vxdisk list DEVICE TYPE DISK GROUP STATUS c1t0d0s2 sliced rootdisk rootdg online c1t1d0s2 sliced error c1t1d0s2 sliced error The extra device will disappear after the next reboot, which seems to be the only way to remove it. Therefore it is best to prevent the duplicate device from being created in the first place. This is accomplished by the following procedure. If the disk is not under VxVM control, you can skip steps 1,2,8-10 Before replacing any disk under VxVM control, it should be either in a 'failed' or 'removed' state. If the disk does not show up as "failed was", as shown here: # vxdisk list DEVICE TYPE c1t0d0s2 sliced c1t1d0s2 sliced DISK rootdisk disk01 GROUP rootdg rootdg STATUS online online failed was:c1t1d0s2

then you should run 'vxdiskadm' and choose option #4 to remove the disk for replacement. After running 'vxdiskadm', the output should look like this: # vxdisk list DEVICE TYPE c1t0d0s2 sliced c1t1d0s2 sliced DISK rootdisk disk01 GROUP rootdg rootdg STATUS online online removed was:c1t1d0s21.

Once the disk is in one of the two states shown above, put the disk into the "offline" state with the following command: # vxdisk offline c1t1d0s22. Verify the disk has been marked "offline" with "vx disk list": # vxdisk list DEVICE TYPE c1t0d0s2 sliced c1t1d0s2 sliced DISK rootdisk disk01 GROUP rootdg rootdg STATUS online offline removed was:c1t1d0s23.

Once Veritas has recognized the disk as offline and ready for replacement, you need to tell the operating system. This is done as follows: # /usr/sbin/luxadm remove_device /dev/rdsk/c1t1d0s2 This will produce output similar to the following: WARNING!!! Please ensure that no file systems are mou nted on these device(s). All data on these devices should have been backed up.

The list of devices which will be removed is: 1: Device name: /dev/rdsk/c1t1d0s2 Node WWN: 20000020371b1f31 Device Type: Disk device Device Paths: /dev/rdsk/c1t1d0s2 Please verify the above list of devices and then enter c or <CR> to Continue or q to Quit. [Default: c]:c stopping: /dev/rdsk/c1t1d0s2.... Done offlining: /dev/rdsk/c1t1d0s2.... Done The drives are now off-line and spun down. Physically remove the disk and press the Return key. Hit <Return> after remov ing the device(s). <date> <systemname> picld[87]: Device DISK1 removed Device: /dev/rdsk/c1t1d0s2 No FC devices found. - /dev/rdsk/c1t1d0s2Note: The picld daemon notifies the s ystem that the disk has been removed. If no errors are printed, continue on to step 4. Otherwise, if you receive any kind of errors during this step: physically pull the bad disk from the host run the commands: # vxdisk rm c1t1d0s2 # luxadm -e offline /dev/rdsk/c1t1d0s2if the disk is multipathed, r un the 'luxadm -e offline' on the second path as well. 4. Initiate devfsadm cleanup subroutines by entering the following command: # /usr/sbin/devfsadm -CThe default devfsadm operation is to attempt to load ev ery driver in the system and attach these drivers to all possible device instanc es. devfsadm then creates device special files in /devices and logical links in /dev. The -C option cleans up the /dev directory and removes any lingering logical lin ks to the device link names. This should remove all the device paths for this particular disk. This can be ve rified with: # ls -ld /dev/dsk/c1t1d*This should return no devices. 5. Verify that the reference to this disk is gone by running the commands # vxdisk list (if the disk is under vxvm control) # formatIt is now safe to physically replace the disk. 6. After replacing the disk, create the necessary entries in the Solaris device tree with the following the command: # devfsadm -Cor # /usr/sbin/luxadm insert_device <enclosure_name,sxwhere x is the slot number. Use # luxadm display <enclosure_name>to find the slot number. To find the <enclosu re_name> you can use # luxadm probeRun "ls -ld /dev/dsk/c1t1d*" to verify the new device paths have been created.

7. Label the disk using format. If the disk is under VxVM control, be sure to wr ite a SMI label: # format -e /dev/rdsk/c1t1d0s2 ... format> l [0] SMI Label [1] EFI Label Specify Label type[1]: 0 Auto configuration via format.dat[no]? no Auto configuration via generic SCSI-2[no]? yes Ready to label disk, continue? yesIf the disk is not under VxVM control you ca n label the disk to your requirements else you might simply label it with a stan dard vtoc. 8. Instruct VxVM to re-read the device tree by running the command # vxdctl enable9. The disk will remain in the "offline" state until you ini tialize the new disk. To initialize it, use either the command line # vxdisksetup -i c1t1d0or run 'vxdiskadm' and choose option #5 to initializ e it and replace the failed or removed disk. If you choose to run 'vxdiskadm' and choose option #5, you will be told that "Access is disabled" for this new disk (because it is still "offline"), and will be asked whether or not you wish to "enable access" to it. Answer 'yes' to this question. 10. Your disk should now be online, and functional within the operating system and VxVM. You can confirm this with "vxdisk list".