Move of the Cluster Shared Volume resource Cluster Virtual Disk is vetoed because there is a Data Integrity Scan is in progress on one of the volumes belonging to the resource. Please retry the action after the operation is completed.

Michael Mazzucca 51 Reputation points
2023-07-24T08:05:16.55+00:00

Hi,

We have a 2 Node Azure Stack HCI 22H2 Cluster with multiple CSV.

When we try to move some CSV to another node to install Updates we got the error Message:
Move of the Cluster Shared Volume resource 'Cluster Virtual Disk ' is vetoed because there is a Data Integrity Scan is in progress on one of the volumes belonging to the resource. Please retry the action after the operation is completed.

with Event ID 5162

Some CSV work as expected.

We tried to start the Scheduled Task "Data Integrity Check And Scan". After finish with no errors nothing changed.

Maybe there is a Flag on the CSV we can change?

We didn't want to move all VM to another CSV and rebuild the volume!

Thanks for you help

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
237 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
939 questions
{count} vote

Accepted answer
  1. kobulloc-MSFT 21,836 Reputation points Microsoft Employee
    2023-08-18T00:59:09.9466667+00:00

    Hello, @Michael Mazzucca !

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

    Issue:

    When we try to move some CSV to another node to install Updates we got the error Message:

    Move of the Cluster Shared Volume resource 'Cluster Virtual Disk ' is vetoed because there is a Data Integrity Scan is in progress on one of the volumes belonging to the resource. Please retry the action after the operation is completed.

    with Event ID 5162

    Solution:

    Provided by Michael Mazzucca:

    The fix was to run manualy the Data Integrity Scan for Crash Recovery task on all Nodes. After the tasks has been finshed on all nodes (can take a while) moving of the CSV was possible again.

    Provided by Vigo Sun:

    I need to run those command on ALL my cluster nodes and then the issue is resolved.

    Get-ScheduledTask "Data Integrity scan for*" | Start-ScheduledTask

    Remember to run it on all Nodes, hope it can solve your issue.

    Thank you again for updating us with the solution! If you get a moment, please accept one of the answers here to increase the visibility of this solution.

    User's image

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Vigo Sun 5 Reputation points
    2023-08-03T14:13:38.73+00:00

    Hello there,

    The issue has been resolved by opened a case with Microsoft.

    I need to run those command on ALL my cluster nodes and then the issue is resolved.

    Get-ScheduledTask "Data Integrity scan for*" | Start-ScheduledTask

    Remember to run it on all Nodes, hope it can solve your issue.

    Thanks,

    Vigo

    1 person found this answer helpful.

  2. Michael Mazzucca 51 Reputation points
    2023-08-17T08:58:14.8733333+00:00

    So with MS Support we were able to resolve the issue.

    The fix was to run manualy the Data Integrity Scan for Crash Recovery task on all Nodes.

    After the tasks has been finshed on all nodes (can take a while) moving of the CSV was possible again.

    Thanks to all who helped

    1 person found this answer helpful.