hp workstations zx6000, hp server rx2600 - operation and maintenance guide

Product Information

Hot-Swappable/Pluggable Devices

Chapter 1

The system problem for this example is that the disk at hardware address 10/0/13/0.0

has a head crash, and as a result, is unusable. The steps described in the Hot-Plug

Procedure section below outline a method that can be used to recover from this state.

1. All of the replaced disk’s in-use extents must belong to mirrored logical volumes

which were created with the “strict” option (-s); see the documentation for

MirrorDisk/UX.

2. You must have an up-to-date conﬁguration backup ﬁle. This is done automatically

each time an LVM command changes LVM conﬁguration.

The default backup ﬁle’s path is:

/etc/lvmconf/<base_vg_name>.conf

For example,

/etc/lvmconf/vg00.conf

3. The replacement disk must be the same product ID as the replaced one.

NOTE HP often uses different manufacturers for disks having the same product number. The

hot-plug manual procedure will not update the disk driver’s internal information to that

of the replaced disk.

The replacement disk will have the same capacity and block size as the defective disk

because they have the same product number. The only ﬁeld that could be incorrect is the

string specifying the vendor’s name. This will not affect the behavior of the LVM. If it is

desired to update the manufacturer’s name, the disk’s volume group must be deactivated

and reactivated. See the HP-UX System Administration Tasks manual for details.

Hot-Plug Procedure

These are the steps required to properly hot-plug a disk drive:

Step 1

• Check if the LVM found the physical volume to be defective when the volume group

was activated.

• The command “vgchange -a y” would have printed the following message on the

console:

WARNING:

VGCHANGE:WARNING: COULDN’T ATTACH TP THE VOLUME GROUP

PHYSICAL VOLUME “/DEV/DSK/cXtXdX”

THE PATH OF THE PHYSICAL VOLUME REFERS TO A DEVICE THAT DOES NOT

EXIST, OR IS NOT CONFIGURED INTO THE KERNEL.

• If the status of the “vgchange -v vg02” is unknown, you may check if this occurred

by doing a vgdisplay<VG name> command. For example:

vgdisplay /dev/vg00