This procedure assumes that you have the following resources available:
root file system is of type
ufs, you can back it up using the
This procedure requires the reinstallation of the root disk. To prevent the loss of data on disks not involved in the reinstallation, only involve the root disk in the reinstallation procedure.
Several of the automatic options for installation access disks other than the root disk without requiring confirmation from the administrator. Therefore, disconnect all other disks containing volumes from the system prior to starting this procedure. This will ensure that these disks are unaffected by the reinstallation. Reconnect the disks after completing the procedure.
The procedure assumes the device name of the new root disk to be
c0t0d0s2, and that you need to recover both the
/) file system on partition
s0, and the
/usr file system on partition
To recover a root disk and root mirror from a backup
boot cdrom -s
format command to create partitions on the new root disk (
c0t0d0s2). These should be identical in size to those on the original root disk before encapsulation unless you are using this procedure to change their sizes. If you change the size of the partitions, ensure that they are large enough to store the data that is restored to them.
format(1M) manual page.
A maximum of five partitions may be created for file systems or swap areas as encapsulation reserves two partitions for Veritas Volume Manager
mkfs command to make new file systems on the
usr partitions. For example, to make a
ufs file system on the
root partition, enter:
mkfs -F ufs /dev/rdsk/c0t0d0s0
mkfs(1M) manual page.
mkfs_ufs(1M) manual page.
/dev/dsk/c0t0d0s0 on a suitable mount point such as
mount /dev/dsk/c0t0d0s0 /a
root file system from tape into the
/a directory hierarchy. For example, if you used
ufsdump to back up the file system, use the
ufsrestore command to restore it.
ufsrestore(1M) manual page.
installboot command to install a bootblock device on
/usr file system is separate from the root file system, use the
mkdir command to create a suitable mount point, such as
/a/usr/, and mount
/dev/dsk/c0t0d0s6 on it:
mkdir -p /a/usr
mount /dev/dsk/c0t0d0s6 /a/usr
/usr file system is separate from the root file system, restore the
/usr file system from tape into the
/a/usr directory hierarchy.
root file system.
/a/etc/vx/reconfig.d/state.d/install-db to prevent the configuration daemon,
vxconfigd, from starting:
/a/etc/system to a backup file such as
/a/etc/system by putting a
* character in front of them:
These lines should then read:
* set vxio:vol_rootdev_is_volume=1
/a/etc/vfstab to a backup file such as
/a/etc/vfstab, and replace the volume device names (beginning with
/dev/vx/dsk) for the
/usr file system entries with their standard disk devices,
/dev/dsk/c0t0d0s6. For example, replace the following lines:
/dev/vx/dsk/rootvol /dev/vx/rdsk/rootvol / ufs 1 no -
/dev/vx/dsk/usrvol /dev/vx/rdsk/usrvol /usr ufs 1 yes -
with this line:
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no -
/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr ufs 1 yes -
0 command, and reboot from the new root disk. The system comes up thinking that VxVM is not installed.
usrvol) from the
rm -r /etc/vx/reconfig.d/state.d/install-db
Start the Veritas Volume Manager I/O daemons:
vxiod set 10
Start the Veritas Volume Manager configuration daemon in disabled mode:
vxconfigd -m disable
Enable the old boot disk group excluding the root disk that VxVM interprets as failed::
vxedit command (or the Veritas Enterprise Administrator (VEA)) to remove the old root disk volumes and the root disk itself from Veritas Volume Manager control.
vxdiskadm command to encapsulate the new root disk and initialize any disks that are to serve as root disk mirrors. After the required reboot, mirror the root disk onto the root disk mirrors.