Migrating vPar Systems to Integrity VM

11 of 13
Reconfigure the Root Volume Group
Once the system is up in single-user mode, you need to reconstruct the root volume group. This is
accomplished by proceeding as follows:
1. Create the device filenames
# insf –e
2. Identify the device filename of the boot device
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 8 0/0/0/0.0.0 sdisk CLAIMED DEVICE HP Virtual Disk
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
/dev/dsk/c5t0d0s1 /dev/rdsk/c5t0d0s1
/dev/dsk/c5t0d0s2 /dev/rdsk/c5t0d0s2
/dev/dsk/c5t0d0s3 /dev/rdsk/c5t0d0s3
/dev/dsk/c5t0d0s4 /dev/rdsk/c5t0d0s4
/dev/dsk/c5t0d0s5 /dev/rdsk/c5t0d0s5
/dev/dsk/c5t0d0s6 /dev/rdsk/c5t0d0s6
/dev/dsk/c5t0d0s7 /dev/rdsk/c5t0d0s7
3. Run vgscan to get the device filenames grouped with the boot device
# vgscan
vgscan: Warning: couldn't query physical volume "/dev/dsk/c2t1d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query all of the physical volumes.
Physical Volume "/dev/dsk/c5t0d0s4" contains no LVM information
Physical Volume "/dev/dsk/c5t0d0s5" contains no LVM information
Physical Volume "/dev/dsk/c5t0d0s6" contains no LVM information
Physical Volume "/dev/dsk/c5t0d0s7" contains no LVM information
Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c5t0d0s2
The Volume Group /dev/vg00 was not matched with any Physical Volumes.
4. Remove the old root volume group information
# vgexport /dev/vg00
5. Create a location for the root volume group
# mkdir /dev/vg00
# mknod /dev/vg00/group c 64 0x00000
6. Import the root volume group information for the new hardware path using the device filename
identified in steps 2 and 3 above. (In this example, /dev/dsk/c5t0d0s2.)
# vgimport -m /mapfile.vg00 /dev/vg00 /dev/dsk/c5t0d0s2
vgimport: Warning: Volume Group belongs to different CPU ID.
Can not determine if Volume Group is in use on another system.
Continuing.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after
activating the volume group.