Error 'Failed to get volume information' and 'Volume not present' Error: 99 reported for the MountV resource in Veritas Cluster Server (VCS)

book

Article ID: 100002526

calendar_today

Updated On:

Description

Error Message

The errors below are reported in the  %VCS_HOME%\log\Mountv_A.log file:

VCS WARNING V-16-10051-9043 MountV::monitor:Failed to get volume information [19:99]

VCS ERROR V-16-50-0 MountV::monitor:GetDgVolumeGuid failed. Error: 99
    LibVMObj.cpp:VLibVMObj::GetVolGUID[1350]

VCS ERROR V-16-50-0 MountV::monitor:Volume not present
    MountV.c:MountV_monitor[296]

 

Cause

This issue has been seen when the Disk Group successfully imports; however, the volume doesn't arrive due to a problem between Windows PNP and InfoScale. 

This issue occurs when the value for the Volume Name attribute specified for the MountV resource in VCS does not match the value for the Volume Name attribute for the corresponding volume in Veritas Enterprise Administrator (VEA).

 

Resolution

First, clear any faults in the cluster and bring the Volume Manager Diskgroup (VMDg) resource online in the cluster, but do not bring any of the MountV resources online to avoid a fault. In the Veritas Enterprise Administrator console, check if the problem (volume) for the MountV resource(s) shows in an "offline" status. If so, right-click on the Volume and select the "reactivate" option to force the volume arrival process to see if it then comes online. If so, continue bringing up the rest of the Service Group in the cluster. If not, continue on with the second possible cause/solution provided below. 

To ensure that the Volume Name attribute is a match between VCS and VEA, the below steps can be performed:

1. From VEA, highlight the volume for which the MountV resource is configured. On the right-hand side pane, it will list the Volume name field as seen below:

 

2) Browse to VCS, to the MountV resource and ensure the same value is listed in the Volume Name attribute

If the values do not match, then edit the value in VCS using the below steps to match it with VEA.

 

a) Click on the Edit button for the Volume Name as shown below

 

b) Enter the same value as VEA and click OK

 

c) Right click on the MountV resource and select Probe

 

d) It should now be able to probe and any attempts to online the MountV resource will be completed successfully.

Issue/Introduction

For Veritas Cluster Server (VCS) on the Windows platform, the MountV resource fails to probe, thereby preventing it from coming online.