Error Code details
V-5-1-7935
Severity: Error 
Component: Volume Manager 
Message:
Disk group %s: update failed: %s
Description:

There’s a second part of the error message, which varies depending on the context. The following table shows where to find the description and solution for each message.

 

Messages

See…

Disk group has no valid configuration copies

Solution 1 & Solution 2

System error in configuration copy

Solution 2

Internal configuration daemon error

Solution 3

Memory allocation failure

Solution 4

 

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2013-06-20 03:24:09 PDT
Platform: Solaris 10 (SPARC), Solaris 10 (x86-64)
Release: 5.1
Content:

Description:

 

Veritas Volume Manager (VxVM) compares the unique disk identifier (UDID) that is known to the device discovery layer (DDL) with the UDID set in the disk’s private region. If the values differ, the udid_mismatch and any clone_disk flags are set on the disk. VxVM disallows the mix of cloned (UDID_mismatch) and non-cloned (non-UDID_mismatch) disks in the same disk group. And then during the import of the disk group, VxVM skips the cloned disks. The non-cloned disks thus fail to obtain enabled or valid configuration copies. As VxVM cannot update the configuration copies of the disk group, it disables the disk group. And disk group auto-import fails during boot time.

 

Solution:

 

The issue only happens in the releases before VxVM 5.1SP1RP2. You can update your VxVM to 5.1SP1RP2 or higher versions to avoid the problem.

 

Check the status of the disks. Enter:

# vxdisk list

 

If the output shows that the udid_mismatch flags are set, perform the following step. Otherwise go to Solution 2.

 

To solve the problem, clear the clone_disk flags that are related with the cloned devices before you re-import the disk group. Enter the following command lines:

 

# vxdg useclonedev=off import diskgroup

# vxdisk set disk clone=off.

# vxdg -C import diskgroup_name

Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2013-06-19 02:59:34 PDT
Platform: Generic
Release: Generic
Content:

Description:
 

This message is displayed when the Volume Manager (vold) cannot open the disk group configuration copies.

 

Solution:
 

If the udid_mismatch flags are not set, restore the configuration copy by either of the following ways:

 

  1. If the vxconfigbackupd daemon is running, it automatically takes the backup of configuration copies. VxVM starts the daemon during its startup.

     
  2. If you have backups of the configuration copies, you can manually restore them by using the vxconfigrestore command.

Note: Restoration of a disk group configuration requires that the same physical disks are used as were configured in the disk group when the backup was taken.

 

For detailed information on this command, see the vxconfigrestore manual page.

 

Note: This link points to the Storage Foundation and High Availability release 6.0.1, Solaris platform version of the manual page. For the manual page for your release and platform, go to the Documents page on the SORT website.

Solution 3 Vote: [Useful] [Not useful]
Last Modified: 2013-06-20 03:23:48 PDT
Platform: Generic
Release: Generic
Content:

Description:

 

This message is displayed when there’s an internal inconsistency between the vold and vxio, or within vold.

 

Solution:

 

Contact Symantec Technical Support.

Solution 4 Vote: [Useful] [Not useful]
Last Modified: 2013-06-20 03:23:37 PDT
Platform: Generic
Release: Generic
Content:

Description:

 

This message is displayed when the vold cannot allocate memory for buffering when it updates the disk group database file. Possible reasons can be that there’s not enough system memory, or there’s memory leak in the vold.

 

Solution:

 

To decide the reason:

  1. Check the free memory by entering:

# free – m

Or

# top

You can find the memory consumption in the output.

  1. If any processes with a prefix “vx” take unexpected huge memory, there can be a memory leak. In this case, check for the latest patch in which the problem is fixed or contact Symantec Technical Support. You can find all patches at https://sort.symantec.com/patch/finder.
     
  2. Otherwise there can be insufficient memory. And add more memory to the system.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service