Manually editing the file /etc/vx/volboot can result in Volume Manager failing to start. This can be corrected by recreating the /etc/vx/volboot file with the following steps.

First, determine the hostid of the system which in turn determines the volboot.

   vxprivutil list

Example:

# vxprivutil list/dev/dsk/c1t0d0s3
         diskid:  807795954.1095.sys
         group:  name=rootdgid=807795936.1025.sys
         flags:  privateautoimport
         hostid:  sys
                           
This hostid from the above sample shows that the hostid should be the same as the one
in the /etc/vx/volboot file.

If it is different, recreate the volboot file as follows:

         # vxdctlstop
         # vxiod set10  
         # vxconfigd -mdisable
         # vxdctl init

        (where hostid is what it said fromvxprivutil).  

This creates a new  VOLBOOT file.