We have 3-node non-Hyper-V cluster that we use for fileserver resources. The cluster is connected to an MSA 2000i G1 SAN and 2 NETAPP FAS2050s
Every day, two of the volumes hosted by the MSA get 2 x 1038 (Ownership of cluster disk "<foo>" has been unexpectedly lost by the node") errors followed immediately by a 1069 error (Cluster resource '<foo>' in clustered service FS1 failed).
Now one of these volumes is being used by a fileserver resource that hosts the users redirected My Documents folders and we have a strange issue with that drive appearing to be "offline" for some users (all the files and folders are greyed out) and I think this disconnection may be the issue.
I've run a Cluster Validation and everything seems OK but I can't run a full validation as, understandably, we can't take the drives offline during the day.
All the cluster disks are all MPIO-enabled. We don't have the issue with the volumes hosted by the NetApp filers.
I've been investigating this for 48 hours now and I can see nothing that would be obviously causing these two particular disks to experience this issue (though, obviously, there is something!)
Update: I just realised the failure is preceded by multiple 141 (source: NTFS) errors "The description for Event ID 141 from source Ntfs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."