Symantec logo

Restoring a missing or corrupted /etc/vx/volboot file

The following message may be displayed at boot time if the /etc/vx/volboot file is missing or corrupted:

VxVM vxconfigd ERROR V-5-1-1589 enable failed: Volboot file not loaded
transactions are disabled.

VxVM vxconfigd ERROR V-5-2-573 Vold is not enabled for transactions
no volumes started

During system bootup, the VxVM configuration daemon reads the file /etc/vx/volboot. If that file is missing or corrupted, the configuration daemon fails and aborts the boot sequence.

If a recent backup of the /etc/vx/volboot file is available, use that copy to restore the file, and then reboot. If a backup is not available, the following example procedure shows the sequence of commands that you can use to recreate the /etc/vx/volboot file. Replace the disk access name (sda) for the VxVM root disk, host ID (diego) and private region offset (2144) in the example with the values that are appropriate to your system.

 To restore a missing or corrupted /etc/vx/volboot file

  1. Put the system into maintenance mode.
  2. Run vxconfigd in disabled mode:

    # vxconfigd -m disable

  3. Reinitialize the volboot file:

    # vxdctl init diego

    # vxdctl add disk sda privoffset=2144

  4. Reset vxconfigd in boot mode:

    # vxconfigd -kr reset -m boot

  5. Use the following command to confirm that VxVM is running:

    # vxdisk list


    sda sliced rootdisk bootdg online

    sdb sliced rootmir bootdg online

    sdc sliced - - error

  6. Reboot the system.