When Good Disks Go Bad: Dealing with Disk Failures Under LVM (5900-3153, June 2013)

60
Recommended Action:
The volume group extent size and number of physical extents per disk are not dynamic.
The only way to use the entire disk is to re-create the volume group with new values for
the –s and –e options. Alternatively, you can work with an HP support representative to
adjust the volume group characteristics using the vgmodify command; note that this
utility is currently unsupported and available only from your HP support representative.
vgimport
Verification of unique LVM disk id on each disk in the volume group
/dev/vgname failed.
Cause:
There are two possible causes for this message:
a. The vgimport command used the –s option, and two or more disks on the system
have the same LVM identifier; this can happen when disks are created with BCV
copy or cloned with dd.
b. LVM was unable to read the disk header; this can happen when you create new
logical units on a SAN array.
Recommended Action:
a. Do not use the –s option to vgimport. Alternatively, use vgchgid to change the
LVM identifiers on copied or cloned disks.
b. Retry the vgimport command. For a long term solution, install patch PHKL_30510
or one of its superseding patches.
Syslog Error Messages
LVM: VG 64 0x010000: Data in one or more logical volumes on PV 188
0x072000 was lost when the disk was replaced. This occurred because
the disk contained the only copy of the data. Prior to using these
logical volumes, restore the data from backup.
Cause:
LVM cannot synchronize the data on a replaced disk automatically, as when LVM
discovers an unmirrored logical volume residing on a disk that was just replaced. When
all data on a disk is mirrored elsewhere and a copy is available, LVM automatically
synchronizes the data on the replaced disk from the mirrors of the data on other disks.
Recommended Action:
Restore the contents of the logical volume from backup.
LVM: VG 64 0x010000: PVLink 188 0x072000 Detached.
Cause:
This message is advisory and generated whenever a disk path is detached.
Recommended Action:
None.