Home > Hyper-V, Hyper-V R2, Windows 2008 R2 > Cluster shared volume is no longer available on this node Event ID: 5120

Cluster shared volume is no longer available on this node Event ID: 5120

I faced a problem after building a new cluster that I have these error on 2nd node (Passive one) and when I tried to access it explorer hangs

Event ID: 5120
Source: Microsoft-Windows-FailoverCluster
Level: Error
Description: 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.

Event ID generated: 5142
Source: Microsoft-Windows-FailoverCluster
Description: 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

I found all details on MS KB 2008795

Cause:

When accessing a CSV volume from a passive (non-coordinator) node, the disk I/O to the owning (coordinator) node is routed through a ‘preferred’ network adapter and requires SMB be enabled on that network adapter. For SMB connections to work on these network adapters, the following protocols must be enabled:

  • Client for Microsoft Networks
  • File and Printer Sharing for Microsoft Networks

Solution

Review each cluster node and verify the following protocols are enabled the network adapters available for Cluster use

  • Client for Microsoft Networks
  • File and Printer Sharing for Microsoft Networks

1. Click Start , click Run , type ncpa.cpl , and then click OK .
2. Right-click the local area connection that is associated with the network adapter, and then click Properties .
3. Verify that the above protocols appear in the This connection uses the following items box.  If either is missing, follow these steps:
a.  Click Install , click Client , and then click Add .
b.  Select the missing protocol, click OK , and then click Yes .
4. Verify that the check box that appears next to Client for Microsoft Networks is selected.

And in my case I discovered that file and print sharing was not checked on the private connection.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: