Cannot keep clustered storage online

Jeremy Robertson 20 Reputation points
2023-07-31T20:51:21.78+00:00

I have 3 windows server 2019 Hyper-V hosts that connect to DELL PowerVault ME5024 SAN ISCSI target I have the servers connected to the ISCSI target and MPIO configured and it all appears to be working on the server side and the cluster validation Lists the disks and it passes validation. I bring the cluster on line and then add the storage and the storage is see and added and comes online for a couple of minutes then it goes offline and I cannot bring it back online. I am getting an error in the Critical Events "Cluster resource 'Cluster Disk 1' of type 'Physical Disk' in clustered role '5fe2f024-6988-440f-9635-41ce3ce73dde' failed. The error code was '0x571' ('The disk structure is corrupted and unreadable.').

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet."

But the volume shows health in the DELL SAN manager.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,900 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.
1,025 questions
0 comments No comments
{count} votes

Accepted answer
  1. Ian Xue 39,371 Reputation points Microsoft Vendor
    2023-08-01T04:40:55.1466667+00:00

    Hi,

    Please open Disk Managemt on the node currently owns the cluster disk and see if you can format the iSCSI volume manually. Also check the network status and if there is any heavy task running. Run below PowerShell commands to increase the cluster heartbeat tolerance and see if this helps.

    (get-cluster). SameSubnetDelay=2000 
    (get-cluster). SameSubnetThreshold=10  
    (get-cluster). CrossSubnetDelay=4000 
    (get-cluster). CrossSubnetThreshold=20   
    

    Best Regards,

    Ian Xue


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.