Error Code details
Severity: Error 
Component: Storage Foundation Windows 
Failed to deport cluster dynamic disk group.


Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2010-09-24 18:31:23 PDT
Platform: Windows Server 2003 (x86-64), Windows Server 2003 (IA-64), Windows Server 2003 (x86-32), Windows Server 2008 (x86-64), Windows Server 2008 (IA-64), Windows Server 2008 (x86-32), Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016
Release: 5.1

Solution 1

Attempt to manually import the Cluster Disk Group using command  


  • vxdg -g DISKGROUP -f import

This will force import a cluster diskgroup that has 50% or less available disks. But if all of the disks are unavailable or cannot be scsi reserved, this may fail to import the cluster Disk Group with the following message: Failed to complete the operation...V-76-58645-585: Failed to reserve a majority of disks in cluster dynamic disk group.

Should the above error occur, then continue to with the solutions below

Solution 2

Use the command syntax below

  • vxclus.exe ENABLE -g DISKGROUP -p

Details of the above syntax can be found in the article below:

How to use the VxCLUS utility with VERITAS Volume Manager, VERITAS Storage Foundation (SFW) for Windows managing disks in a Microsoft Cluster Server (MSCS) environment, and with Storage Foundation for Windows High Availability (SFW-HA)

However if the Cluster Diskgroup fails to import and shows any of the following messages then continue with other solutions below

V-77-57616-50002: WARNING: Make sure that a majority of the disk group disks are NOT online on any other cluster node before (and after) using this utility. If a majority of the disks are online on another node,
data corruption can occur.  Please consult documentation or technical support for any questions if you are unsure of the usage of the operation. Are you sure you want to proceed with the operation(Y/N)?y

V-77-57616-4037: ****** Enable Force Import for Disk Group DISKGROUP-1

Solution 3

It is possible that a persistent SCSI 3 reservations are preventing the disk from importing and deporting.

Obtain a utility called from Symantec Support and extract it. URL is

This tool can be used to clear SCSI reservations. An example of the syntax would be similar to the following

  • scsicmd -dAll0,1 -sscsi3_release

-dAll0,1 = release reservations on ALL disks except 0 and 1 (because these are local disks, which may be only 0 in your server)

This may be a interim solution as the problem may surface again. Work with the Hardware Vendor to establish correct working practices for SCSI-3 reservation methodology

Solution 4

Obtain the latest Host Bus Adapter (HBA) card drivers and upgrade all the drivers on all the cluster nodes ensuring that all drivers are the same revision. The problem should be resolved after this.

Solution 5

If  this is a MSCS cluster, and the clusters was destroyed while one nodes was down, It will be necessary to run the destroy cluster wizard from that node. This will stop the cluster from placing
a SCSI reservation on the disk once imported.

If the problem persists after following the solutions above, then open a call with Symantec Support to engage in further troubleshooting. Also engage the Hardware Vendor and the Host Bus Adapter manufacturer as both may have specific settings that require enabling in order for reservations to work correctly.


User solutions
No user solutions yet.


Read and accept Terms of Service