Академический Документы
Профессиональный Документы
Культура Документы
A specific procedure must be used when replacing one of the internal disks in a
system with internal fibre drives (Sun Fire[TM] 280R, Sun Fire[TM] V480, Sun
Fire[TM] V490, Sun Fire[TM] V880, Sun Fire[TM] V890), especially if the disk is
under Veritas Volume Manager (VxVM) control.
Although these disks are hot-swappable, the procedure below should be used to
alert VxVM to the fact that the drive is being replaced. This document applies to
Veritas Volume Manager (VxVM) 3.x and above. This document also assumes that you
are running either:
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' command.
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. Steps
9a - 9c pertain only to Sun[TM] Cluster 3.x installations.
If the disk is not under VxVM control, you can skip steps 2,4,9-11
Steps to Follow
NOTE: All data on these devices should have been backed up.
Before replacing any disk under VxVM control, it should be in either a 'failed' or
'removed' state:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 sliced rootdisk rootdg online
c1t1d0s2 sliced - - online
- - disk01 rootdg failed was:c1t1d0s2
If the disk does not show up as "failed was", as shown above, 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 DISK GROUP STATUS
c1t0d0s2 sliced rootdisk rootdg online
c1t1d0s2 sliced - - online
- - disk01 rootdg removed was:c1t1d0s2
NOTE:
If this is a root-disk or root-mirror, check the following removed disk
information, before this operation. This information is needed to change nvramrc.
* WWN
For example,
# ls -al /dev/rdsk/c1t0d0s0
lrwxrwxrwx 1 root root 74 Mar 6 2003 c1t0d0s0 -> ../../
devices/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfa19920,0:a,raw
For example,
# eeprom nvramrc
boot-device=rootdisk mirrdisk
dumpadm -d /dev/dsk/c1t0d0s1
# vxdctl enable
3. Put the disk into the "offline" state with the following command:
4. Verify the disk has been marked "offline" with "vxdisk list":
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 sliced rootdisk rootdg online
c1t1d0s2 sliced - - offline
- - disk01 rootdg removed was:c1t1d0s2
5. Once Veritas has recognized the disk as offline and ready for replacement,
you need to tell the operating system. This is done as follows:
NOTE: The picld daemon notifies the system that the disk has been removed.
# vxdisk rm c1t1d0s2
# luxadm -e offline /dev/rdsk/c1t1d0s2
* if the disk is multipathed, run the 'luxadm -e offline' on the second path
as well.
# /usr/sbin/devfsadm -C -c disk
With the "-c disk" option, devfsadm will only update disk device files. This
saves time and is important on systems that have tape devices attached.
Rebuilding these tape devices could cause undesirable results on non-Sun
hardware.
The -C option cleans up the /dev directory, and removes any lingering
logical links to the device link names.
This should remove all the device paths for this particular disk. This can
be verified with:
# ls -ld /dev/dsk/c1t1d*
7. Verify that the reference to this disk is gone by running the commands
8. After replacing the disk, create the necessary entries in the Solaris OS
device tree with one of the following commands:
# devfsadm
or
NOTE: In many cases, luxadm insert_device does not require the enclosure
name and slot number.
# luxadm probe
Run "ls -ld /dev/dsk/c1t1d*" to verify that the new device paths have been
created.
NOTE: After inserting disk and running devfsadm(or luxadm), the old ssd id
was changed to a new one. So, just ignore this change.
For example:
When an error occurs on the following disks(ssd3).
# 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? yes
If the disk is not under VxVM control, label the disk to local requirements,
otherwise, it could be labeled with a standard vtoc.
9a. /usr/cluster/bin/scdidadm -C
9b. /usr/cluster/bin/scdidadm -r
9c. /usr/cluster/bin/scgdevs
Note: It's possible to get errors from c0t0d0 which is the cdrom/dvd drive on Sun
fire v480,v880 etc..
10. Instruct VxVM to re-read the device tree by running the command
# vxdctl enable
11. The disk will remain in the "offline" state until the new disk is
initialized.
# vxdisksetup -i c1t1d0
Then, use 'vxdiskadm' and choose option #5 to replace the failed or removed
disk.
- OR -
12. The disk should now be online and functional, within the operating system
and VxVM. Confirm this with "vxdisk list".
# vxtask list
dumpadm -d /dev/dsk/c1t1d0s1
14. If this was a root-disk or a root-mirror, then you need to make sure and run
/etc/vx/bin/vxbootsetup command. The vxbootsetup utility configures a disk by
writing a boot track at the beginning of the disk and by creating physical disk
partitions in the UNIX VTOC that match the mirrors of the root, swap, /usr and
/var.
15. If this was a root-disk or root-mirror, then ensure the nvram aliases are
updated so you can boot.
Check the WWN from the ls output with the appropriate root alias entries in
the NVRAM. (eeprom nvramrc) and look at rootmirror or rootdisk entries.
For example,
# eeprom nvramrc
devalias rootdisk
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100004cfa19920,0:a
devalias mirrdisk
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100004cfa19838,0:a
# ls -al /dev/rdsk/c1t0d0s0
lrwxrwxrwx 1 root root 74 Mar 6 2003 c1t0d0s0 ->
../../
devices/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c63f0c94,0:a,raw
- Modify nvramrc
(This example is written in the bourne shell)
# eeprom nvramrc
devalias rootdisk
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c63f0c94,0:a
devalias mirrdisk
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100004cfa19838,0:a
NOTE:
If this is a root-disk or rootmirror, the device path contains the WWN of the
new disk. It is necessary to update the nvramrc devalias entries to the new
device path, so the system will be able to boot from the newly-replaced rootdisk
or rootmirror.
Product