Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 2306

Problems with a volume in a Windows Server 2012 R2 Hyper-V cluster

$
0
0

Hi!

A problem started to arise.
You have a Windows Server 2012 R2 Hyper-V cluster. Three HP Proliant DL380 servers. HP MSA 2050 shared disk subsystem.
An error occurs on the cluster:
The shared cluster volume "Volume7" ("FS-FC") is suspended on the node due to "(c00000b5)". All I / o operations will be temporarily queued until the path to the volume is re-set.
When I look at the Cluster Manager, it already exists in the system. It seems to be temporarily disabled, but it affects the operation of servers and users.

System Center registers an error:
Shared Volume IO is paused warning Description
Warning source: cluster Service
Path: SFH 05.sth. local\Cluster service
Warning rule: Shared Volume IO is paused
Created: 03.04.2020 19: 50:05
The shared cluster volume "Volume7" ("FS-FC") is suspended on the node due to "(c00000b5)". All I / o operations will be temporarily queued until the path to the volume is re-set.

Volume can be other.

Event Details

Event ID:

5120

Source:

Microsoft-Windows-FailoverClustering

Symbolic Name:

http://go.microsoft.com/fwlink/?LinkId=83027

Solutions

CSV - Review events related to communication with the volume

There has been an interruption to communication between a cluster node and a volume in Cluster Shared Volumes. This interruption may be short enough that it is not noticeable, or long enough that it interferes with services and applications using the volume. If the interruption persists, review other events in the System or Application event logs for information about communication between the node and the volume.

If you do not currently have Event Viewer open, see "To open Event Viewer and view events related to failover clustering."

To perform the following procedure, you must be a member of the localAdministrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

...

You can understand that there was a timeout due to the unavailability of the DNS server.
Can anyone have any ideas about this?


Viewing all articles
Browse latest Browse all 2306

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>