In a replicated environment, it may be possible that MountV Resources are not imported correctly and the reason for this is that the volume seems to be corrupt, if the import is due to a failover or to a switch of the ServiceGroup.  Offline / online of the service group on the same node completes without error.

The error that is shown is actually in response to the cluster trying to recover from the fault condition.  The fault condition is that the volume is reporting as being corrupt.

Running CHKDSK or setting AutoFSClean seems to fix the corruption and the Volumes are correctly mounted.

Alternate Solution

As the volume can be offlined and onlined on the same node, its probable that this issue is caused by a delay induced by VVR in providing data access to the volumes, after switching the related DiskGroup to a new node.  Data access is still not granted when MountV import starts and the Volumes are incorrectly recognized as "corrupt", even if no dirty-bit is set.

The issue can be fixed by increasing the MountV attribute OnlineRetryLimit to 1.

This allows the cluster to retry the import (typically after 60 seconds, depending by the Monitor Interval attribute) if the first attempt fails.  On the next occasion the import is tried, data access will be already granted and the import will succeed.