
If the disk is hot-swappable, you can replace it without powering down the system. Otherwise, power
down the system before replacing the disk. For the hardware details on how to replace the disk, see
the hardware administrator’s guide for the system or disk array.
If you powered down the system, reboot it normally. The only exception is if you replaced a disk in
the root volume group.
If you replaced the disk that you normally boot from, the replacement disk does not contain the
information needed by the boot loader. If your root disk is mirrored, boot from it by using the
alternate boot path. If the root disk was not mirrored, you must reinstall or recover your system.
If there are only two disks in the root volume group, the system might fail its quorum check and
might panic early in the boot process with the “panic: LVM: Configuration failure”
message. In this situation, you must override quorum to successfully boot. To do this, interrupt the
boot process and add the –lq option to the boot command normally used by the system. The boot
process and options are discussed in Chapter 5 of Managing Systems and Workgroups (11i v1
and v2) and System Administrator's Guide: Logical Volume Management (11i v3).
Step 3: Initializing the Disk for LVM
This step copies LVM configuration information onto the disk, and marks it as owned by LVM so it can
subsequently be attached to the volume group.
If you replaced a mirror of the root disk on an Integrity server, run the idisk command as described
in step 1 of Appendix D: Mirroring the Root Volume on Integrity Servers. For PA-RISC servers or non-
root disks, this step is unnecessary.
For any replaced disk, restore LVM configuration information to the disk using the vgcfgrestore
command as follows:
# vgcfgrestore –n vgname pvname
If you cannot use the vgcfgrestore command to write the original LVM header back to the new
disk because a valid LVM configuration backup file (/etc/lvmconf/vgXX.conf[.old]) is
missing or corrupted, you must remove the physical volume that is being restored from the volume
group (by using the vgreduce command) to get a clean configuration.
Note: In these situations the vgcfgrestore command might fail to restore the LVM header, issuing
a ‘Mismatch between the backup file and the running kernel’ message. If you are
sure that your backup is valid, you can override this check by using the –R option. To remove a
physical volume from a volume group, you must first free it by removing all of the logical extents. If
the logical volumes on such a disk are not mirrored, the data is lost anyway. If it is mirrored, you must
reduce the mirror before removing the physical volume.
Step 4: Re-enabling LVM Access to the Disk
The process in this step is known as attaching the disk. The action you take here depends on whether
LVM OLR is available.
If you have LVM OLR on your system, attach the device by entering the pvchange command with the
–a and y options as follows:
# pvchange -a y pvname
After LVM processes the pvchange command, it resumes using the device if possible.
If you do not have LVM OLR on your system, or you want to ensure that any alternate links are
attached, enter the vgchange command with the -a and y options to activate the volume group and
bring any detached devices online:
# vgchange -a y vgname
Comentarios a estos manuales