|Article:HOWTO14411|||||Created: 2008-01-08|||||Updated: 2011-11-14|||||Article URL http://www.symantec.com/docs/HOWTO14411|
On system startup, vxconfigd failed to import the disk group associated with the named disk. A message related to the specific failure is given in reason. Additional error messages may be displayed that give more information on the specific error. In particular, this is often followed by:
The most common reason for auto-import failures is excessive numbers of disk failures, making it impossible for VxVM to find correct copies of the disk group configuration database and kernel update log. Disk groups usually have enough copies of this configuration information to make such import failures unlikely.
Configuration records are inconsistent Disk group has no valid configuration copies Duplicate record in configuration Format error in configuration copy Invalid block number Invalid magic number
Failure of an auto-import implies that the volumes in that disk group will not be available for use. If there are file systems on those volumes, then the system may yield further errors resulting from inability to access the volume when mounting the file system.
There may be other error messages that appear which provide further information. See those other error messages for more information on how to proceed. If those errors do not make it clear how to proceed, contact Veritas Technical Support.
Article URL http://www.symantec.com/docs/HOWTO14411