The procedure for replacing a faulty disk mechanism depends
on the type of disk configuration you are using. Separate descriptions
are provided for replacing an array mechanism and a disk in a high
availability enclosure.
For more information, see When Good Disks Go Bad (5991-1236),
posted at http://docs.hp.com
Replacing
a Faulty Array Mechanism |
 |
With any HA disk array configured in RAID 1 or RAID 5, refer
to the array’s documentation for instruction on how to
replace a faulty mechanism. After the replacement, the device itself
automatically rebuilds the missing data on the new disk. No LVM
or VxVM activity is needed. This process is known as hot
swapping the disk.
Replacing
a Faulty Mechanism in an HA Enclosure |
|
If you are using software mirroring with Mirrordisk/UX and
the mirrored disks are mounted in a high availability disk enclosure,
you can use the following steps to hot plug a
disk mechanism:
Identify the physical volume name of the failed disk and the
name of the volume group in which it was configured. In the following examples,
the volume group name is shown as /dev/vg_sg01 and the physical volume name is shown as /dev/dsk/c2t3d0. Substitute the volume group and physical volume names
that are correct for your system.
Identify the names of any logical volumes that have
extents defined on the failed physical volume.
On the node on which the volume group is currently
activated, use the following command for each logical
volume that has extents on the failed physical volume:
# lvreduce -m 0 /dev/vg_sg01/lvolname /dev/dsk/c2t3d0 |
At this point, remove the failed disk and insert
a new one. The new disk will have the same HP-UX device name as
the old one.
On the node from which you issued the lvreduce command, issue the following command to restore
the volume group configuration data to the newly inserted disk:
# vgcfgrestore -n /dev/vg_sg01 /dev/dsk/c2t3d0 |
Issue the following command to extend the logical
volume to the newly inserted disk:
# lvextend -m 1 /dev/vg_sg01 /dev/dsk/c2t3d0 |
Finally, use the lvsync command for each logical volume that
has extents on the failed physical volume. This synchronizes
the extents of the new disk with the extents of the other mirror.
# lvsync /dev/vg_sg01/lvolname |
Replacing
a Lock Disk |
|
Replacing a failed lock disk mechanism is the same as replacing
a data disk. If you are using a dedicated lock
disk (one with no user data on it), then you need to issue only
one LVM command, as in the following example:
# vgcfgrestore -n /dev/vg_lock /dev/dsk/c2t3d0 |
Serviceguard checks the lock disk on an hourly basis. After
the vgcfgrestore command, review the syslog file of an active cluster
node for not more than one hour. Then look for a message showing
that the lock disk is healthy again.
On-line
Hardware Maintenance with In-line SCSI Terminator |
|
In some shared SCSI bus configurations, on-line SCSI disk
controller hardware repairs can be made if HP in-line terminator
(ILT) cables are used. In-line terminator cables are supported with
most SCSI-2 Fast-Wide configurations.
In-line terminator cables are supported with Ultra2 SCSI host
bus adapters only when used with the SC10 disk enclosure. This is
because the SC10 operates at slower SCSI bus speeds, which are safe
for the use of ILT cables. In-line terminator cables are not supported
for use in any Ultra160 or Ultra3 SCSI configuration, since the
higher SCSI bus speeds can cause silent data corruption when the
ILT cables are used.
Printable version
