<\/p>\n
this can happens for many reasons starting from storage disconnections, ISCSI network problems,Bad subnet’s IP’s for ISCSI network with Stuck Switches as well as Active Directory errors like miss configure DNS server, wrong cluster configuration on DC and more.<\/p>\n
Some time the error codes are simple and clear but some time it can be laconic and not clear enough to understand what went wrong .<\/p>\n
for example Event ID 5120:<\/p>\n
\nEvent ID: 5120
\nSource: Microsoft-Windows-FailoverCluster
\nLevel: Error
\nDescription: Cluster Shared Volume “volume_name” is no longer available on this node because of “STATUS_BAD_NETWORK_PATH(c00000be)’. All I\/O will temporarily be queued until a path to the volume is re-established.<\/p>\nEvent ID: 5120
\nSource: Microsoft-Windows-FailoverCluster
\nLevel: Error
\nDescription: Cluster Shared Volume “volume_name” is no longer available on this node because of ‘STATUS_CONNECTION_DISCONNECTED(c000020c)’. All I\/O will temporarily be queued until a path to the volume is reestablished.<\/p>\nEvent ID: 5120
\nSource: Microsoft-Windows-FailoverCluster
\nLevel: Error
\nDescription: Cluster Shared Volume “volume_name” is no longer available on this node because of ‘STATUS_MEDIA_WRITE_PROTECTED(c00000a2)’. All I\/O will temporarily be queued until a path to the volume is reestablished.<\/p>\nEvent ID generated: 5142
\nSource: Microsoft-Windows-FailoverCluster
\nDescription: Cluster Shared Volume “volume_name” (‘Cluster Disk #’) is no longer accessible from this cluster node because of error ‘ERROR_TIMEOUT(1460)’. Please troubleshoot this node’s connectivity to the storage device and network connectivity.<\/p><\/blockquote>\nYou can get this error with out really understand What the hell went wrong. apparently this error codes come from SMB error codes, full list here<\/a>.<\/p>\n
\n\n\nSometime it can happens when accessing\u00a0a CSV volume from a\u00a0passive (non-coordinator)\u00a0node, the disk I\/O\u00a0to the owning (coordinator) node\u00a0is routed through\u00a0a ‘preferred’ network adapter and requires SMB be enabled on that\u00a0network adapter. For SMB connections to work on these network adapters, the following\u00a0protocols\u00a0must be\u00a0enabled:<\/p>\n
just check you have this protocols on the network adapter<\/p>\n
\n
- Client for Microsoft Networks<\/li>\n
- File and Printer Sharing for Microsoft Networks<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n
In any case you should check SMB connection between all nodes as well, First check the version and connections. Run from PowerShell on Hyper-V Node :<\/p>\n
PS C:\\> Get-SmbConnection<\/pre>\nThen run<\/p>\n
PS c:\\> Get-SmbClientConfiguration<\/pre>\n