Microsoft posted a KB article for when you have a situation on W2008, W2008 R2 or WS2012 where a cluster fileshare resource fails on a failover cluster node and the cluster log contains "status 5. Tolerating…".
Symptoms
Consider the following scenario:
- In Windows Server 2008, 2008 R2 or 2012 you set up a Windows failover cluster with a highly available file server.
- The cluster nodes are configured with a disjointed namespace in which the computer’s primary DNS suffice does not match the DNS domain of which it is a member.
In this scenario, you may notice that the highly available file server works fine on some of the cluster nodes but consistently fails on others. In examining the cluster log, you see something similar to the following entries with the first entry referring to "status 5. Tolerating…":
00001b6c.000008c8::2013/01/23-04:00:13.797 WARN [RES] File Server <FileServer-(yoel-cluster)(Cluster Disk 6)>: Failed in NetShareGetInfo(yoel-cluster, share2), status 5. Tolerating…
00001b6c.000008c8::2013/01/23-04:00:13.797 ERR [RES] File Server <FileServer-(yoel-cluster)(Cluster Disk 6)>: Not a single share among 1 configured shares is online
00001b6c.000008c8::2013/01/23-04:00:13.797 ERR [RES] File Server <FileServer-(yoel-cluster)(Cluster Disk 6)>: File system check failed, number of shares verified: 1, last share status: 5.
00001b6c.000008c8::2013/01/23-04:00:13.797 ERR [RES] File Server <FileServer-(yoel-cluster)(Cluster Disk 6)>: Fileshares failed health check during online, status 5.Cause
One or more nodes of the failover cluster may contain mismatched entries in the DNS suffix search list.
Resolution
To resolve the issue, verify all cluster nodes are configured with the same DNS suffix search list and the entries are listed in the same order. The DNS suffix search list can be modified using the following steps:
- Open the properties page for the network adapter.
- Open the properties page for Internet Protocol Version 4 (TCP/IPv4).
- Select the Advanced button under the General tab.
- Select the DNS tab.
This is a configuration issue and there is no hotfix.