Windows 2008 Failover Cluster disk problem with Event ID 1037, 1069 and 1034

Windows 2008 Failover Cluster disk problem with Event ID 1205, 1037, 1069 and 1034

We are running Windows 2008 R2 and created a Failover Clustering. One of node Disk Management shows shared disk is "Reserved" as shown below and can't be see it in the Windows Explorer.

The Event Viewer logs following IDs:

Event ID 1037: The file system for one or more partitions on the disk for resource 'Cluster Disk 1' may be corrupt. Run the Validate a Configuration wizard to check your storage configuration. Optionally, you may want to run Chkdsk to verify the integrity of all volumes on this disk.

Event ID 1069: Cluster resource 'Cluster Disk 1' in clustered service or application 'Cluster Group' failed.

Event ID 1034: Cluster physical disk resource 'Cluster Disk 1' cannot be brought online because the associated disk could not be found. The expected signature of the disk was '5D75C3BD'. If the disk was replaced or restored, in the Failover Cluster Manager snap-in, you can use the Repair function (in the properties sheet for the disk) to repair the new or restored disk. If the disk will not be replaced, delete the associated disk resource.

Event ID: 1205
Description:The Cluster service failed to bring clustered service or application 'e458ac69-c6d0-4357-8afc-269c13f4c633' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

The Reserved Disk can't be turn on. How do you fix it?

Case 1: There is a network issue and cluster can't access one of iSCSI drive.

Case 2: It could be Failover cluster configuration issue or replication software issue. Please refer to this post:

Virtual Machine Configuration Failed Issues in Microsoft Failover ...

Case 3: A disk has become unavailable or inaccessible, and therefore, the Cluster service cannot find it. Please check this post: Event ID 1034 cluster disk resource could not be found

Case 4: The signature on the disk has been changed. Please check this post: Event ID 1034 cluster disk resource could not be found

Case 5: it could be other node down and can't be reached.

Post your questions, comments, feedbacks and suggestions

Contact a consultant