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

Note: You cannot run vxdarestore if c#t#d# naming is in use. Additionally,
vxdarestore does not handle failures on persistent simple or nopriv disks that
are caused by renaming enclosures, by hardware reconfiguration that changes
device names. or by removing support from the JBOD category for disks that
belong to a particular vendor when enclosure-based naming is in use.
See “Removing the error state for persistent simple or nopriv disks in the boot
disk group” on page 104.
See “Removing the error state for persistent simple or nopriv disks in non-boot
disk groups” on page 105.
See the vxdarestore(1M) manual page.
Removing the error state for persistent simple or nopriv disks
in the boot disk group
If all persistent simple and nopriv disks in the boot disk group (usually aliased as
bootdg) go into the error state, the vxconfigd daemon is disabled after the naming
scheme change.
Note: If not all the disks in bootdg go into the error state, you need only run
vxdarestore to restore the disks that are in the error state and the objects that
they contain.
To remove the error state for persistent simple or nopriv disks in the boot disk
group
1
Use vxdiskadm to change back to c#t#d# naming.
2
Enter the following command to restart the VxVM configuration daemon:
# vxconfigd -kr reset
3
If you want to use enclosure-based naming, use vxdiskadm to add a
non-persistent simple disk to the bootdg disk group, change back to the
enclosure-based naming scheme, and then run the following command:
# /etc/vx/bin/vxdarestore
Administering disks
Changing the disk-naming scheme
104