Veritas Volume Manager 5.0.1 Administrator's Guide, HP-UX 11i v3, First Edition, November 2009

Note: This release only supports the conversion of LVM version 1 volume groups
to VxVM. It does not support the conversion of LVM version 2 volume groups.
See the Veritas Volume Manager Migration Guide.
Using vxdiskadd to put a disk under VxVM control
To use the vxdiskadd command to put a disk under VxVM control.
◆
Type the following command:
# vxdiskadd disk
For example, to initialize the second disk on the first controller:
# vxdiskadd c0t1d0
The vxdiskadd command examines your disk to determine whether it has
been initialized and also checks for disks that have been added to VxVM, and
for other conditions.
If you are adding an uninitialized disk, warning and error messages are
displayed on the console by the vxdiskadd command. Ignore these messages.
These messages should not appear after the disk has been fully initialized;
the vxdiskadd command displays a success message when the initialization
completes.
The interactive dialog for adding a disk using vxdiskadd is similar to that for
vxdiskadm.
See “Adding a disk to VxVM” on page 107.
Rootability
Rootability indicates that the volumes containing the root file system and the
system swap area are under VxVM control. Without rootability, VxVM is usually
started after the operating system kernel has passed control to the initial user
mode process at boot time. However, if the volume containing the root file system
is under VxVM control, the kernel starts portions of VxVM before starting the
first user mode process.
Under HP-UX, a bootable root disk contains a Logical Interchange Format (LIF)
area. The LIF LABEL record in the LIF area contains information about the starting
block number, and the length of the volumes that contain the stand and root file
systems and the system swap area. When a VxVM root disk is made bootable, the
Administering disks
Rootability
112