SORT

Veritas™ Services and Operations Readiness Tools (SORT)

Error Code details
V-5-1-1589
Severity: Error 
Component: Volume Manager 
Message:
enable failed: <error_details>
Description:

This message is displayed when the regular startup of vxconfigd fails. It can also be a result of the vxdctl enable command. This message has several error_details:

  • enable failed: Volboot file not loaded

VxVM (Veritas Volume Manager) does not start during boot up after installation. The most possible reason is that the install-db file exists. It causes VxVM not to start up automatically during boot up and volboot file was not created properly during installation.

  • enable failed: aborting

    The failure is fatal and vxconfigd is forced to exit. The most possible reason is that the operating system is unable to create inter-process communication channels to other utilities.
     
  • enable failed: Error check group configuration copies. Database file not found

    The directory /var/vxvm/tempdb is inaccessible. The possible reasons are:
     

  • The root file system has corrupted.
     

  • The root file system is full.
     

  • If /var is a separate file system, it has corrupted or not been mounted.
     

  • enable failed: transactions are disabled

    This message may be followed by other error messages. In this situation, vxconfigd continues to run, but no configuration updates are available until the real problem is fixed.

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2014-09-18 09:38:57
Platform: Generic
Release: Generic
Content:

Generally, you can restart vxconfigd with -k –x 9 option. The output contains more information from which you can diagnose the real problem. The following is an example of the output.

>> # vxconfigd -k -x 9

03/15 04:45:49:  VxVM vxconfigd DEBUG V-5-1-24577

VOLD STARTUP pid=8074 debug-level=9 logfile=

03/15 04:45:49:  VxVM vxconfigd DEBUG V-5-1-681 IOCTL SET_KLICENSE licenses: basic concat span mirror stripe raid5 orm vvrclustering-full: return 0(0x0)

03/15 04:45:49:  VxVM vxconfigd DEBUG V-5-1-681 IOCTL GET_VOLINFO: return 0(0x0)

03/15 04:45:49:  VxVM vxconfigd DEBUG V-5-1-21879 Kernel version 6.0

03/15 04:45:49:  VxVM vxconfigd DEBUG V-5-1-681 IOCTL GET_VOLINFO: return 0(0x0)

03/15 04:45:49:  VxVM vxconfigd DEBUG V-5-1-21879 Kernel version 6.0

03/15 04:45:49:  VxVM vxconfigd DEBUG V-5-1-681 IOCTL KTRANS_ABORT: failed: errno=22 (Invalid argument)

…

 

Note: You can use the vxdctl debug level command to change the debug level back after resolving the problem.

  • For enable failed: aborting and enable failed: transactions are disabled

Restart vold with  -x 9 option, and then make the changes according to the output.

  • For enable failed: Error check group configuration copies. Database file not found
    • If the root file system is full, increase its size or remove files to make space for the tempdb file.
    • If /var is a separate file system, make sure that it has an entry in /etc/fstab. Otherwise, refer to the I/O error messages during the boot process. The I/O error messages may indicate either a hardware problem or a mis-configuration of any logical volume-management software that is used for the /var file system. Also make sure that the encapsulation (if configured) of your boot disk is complete and correct.
  • For enable failed: Volboot file not loaded
  1. Remove the install-db file so that VxVM will automatically start during boot up.
  2. Create volboot file by running the following command: # vxdctl init
  3. Enable VxVM by running the following command: # vxdctl enable
  4. Check if VxVM is now in enable mode by running the following command: # vxdctl mode
  5. Check if you can now run Veritas commands such as: # vxdisk list

For more details about enable failed: Volboot file not loaded, see http://www.symantec.com/docs/TECH124751

 

For the message that is related to vxdctl enable in the same V-5-1-1589, see www.symantec.com/docs/TECH75640.