Causes

• The private regions of all disks in a disk group have become unreadable or corrupted.
• Check for disk, HBA, or array hardware failures. Check event log and vold log for I/O errors
• The disks themselves are not readable/write-protected
• The disks are possibly stale paths for existing available disks to the server
• The disks have mismatched DiskSet IDs 

1. Use the SCSICMD tool to identify if the disk is reserved by another host. The tool is available at - How to use the SCSIcmd utility to perform various SCSI-2 and SCSI-3 reservation related actions

An output for scsi3_query or scsi2_query, will report similar output as below if a possible SCSI reservation

This can be released using the scsi3_release/Scsi2_release command or can be worked with Storage team to remove the SCSI reservation

2. To confirm if the disk is write-protected, attempt to perform a reserve for the disk using the SCSI reservation commands from  How to use the SCSIcmd utility to perform various SCSI-2 and SCSI-3 reservation related actions

If the media is write-protected, it would provide output similar to below

3. If Veritas multipathing is involved, make sure none of the Veritas DSM drivers show up with a Yellow bang in the Device Manager->System Devices. If so, then please attempt a repair/upgrade for the DSM Drivers . 

4. If third party multipathing is involved, make sure all the paths are Healthy and Intact for all the disks 

5. If none of the above hold true for the environment, please contact Veritas Support for assistance to attempt recovery of the disk group configuration.

V-76-58645-182 - INTERNAL Error - Dynamic disk group has no valid configuration copies.