PING : REPLACING AN LVM DISK : CHAPTER 3
|
Replacing a root disk WITHOUT LVM mirroring With the failure of the boot disk, you will have lost the information on disk that is required to be able to boot the system. So, you will need to install at least a minimal system onto the boot disk, and then restore your original kernel and operating system files from your backup. Example configuration:
Volume group /dev/vg00 contains the three disks, with the logical
volume configuration as shown:
|---------| |---------| |---------|
| lvol 1 | | lvol 3 | | lvol 5 |
|---------| |---------| |---------|
| lvol 2 | | lvol 4 | | lvol 6 |
|---------| |---------| | |
| lvol 3 | | lvol 5 | | |
|---------| |---------| |---------|
hardware address 52.6.0 52.5.0 52.4.0
device file c0t0d0 c0t1d0 c0t2d0
(/dev/dsk/)
The scenario for this chapter is that the disk at hardware
address
52.6.0 has a head crash, and as a result is unusable. Our
example
is a worst case example where /usr
(lvol3) spans over from the
faulty disk to another one. lvol3
has 300 Mb on the disk at
52.6.0,
and another 100 Mb on the disk at 52.5.0.
Our root logical
volume
was installed with 104 Mb (lvol1), and swap
(lvol2) of 48 Mb.
The
aim of the steps below is to allow a recovery in which you will
have
to recover the data for logical volumes 1, 2 and 3, but not for
any
of the other logical volumes in the volume group. They all
reside
on disks that are still OK, so we shouldn't have to touch their
data.
COPYUTIL USERS: If you used COPYUTIL to create a disk image, you will not have to do the following steps, except for Step 3.6 to restore your most recent data. Additionally, if you have added a file system/lvol since using COPYUTIL, you will also need to do Step 3.12 and Step 3.13. Instead, you can restore your disk image. For instructions on how to do this, refer to the "Support Media User's Guide", part number 92453-90010. |
