When it comes to setting up a new node in a Windows cluster and configuring AlwaysOn Availability Databases, it’s common for users to simply go with the default settings and click “Finish.” However, this can sometimes lead to unexpected issues and errors.
Recently, one of my clients encountered a problem while adding a new node to their AlwaysOn Availability Group in their test environment. After adding the node to the Windows cluster, they noticed that the databases, which were part of the availability group, went into a not synchronizing state. Upon further investigation, they discovered that the local disks were added to the cluster under “available storage.”
Upon reviewing the event log, they found the following error:
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Event ID: 1069
Task Category: Resource Control Manager
Level: Error
Description: Cluster resource 'Cluster Disk 2' of type 'Physical Disk' in clustered role 'Available Storage' failed. The error code was '0x1' ('Incorrect function.')
After analyzing the situation, I realized that they had most likely followed the default settings in the wizard and forgotten to uncheck a certain checkbox. This checkbox, which is enabled by default, has caused issues for many, including myself during demos.
The solution to this problem is to remove the disk resource from the Failover Cluster Manager. Once this is done, the drives need to be brought online in Disk Management after they are removed from the Failover Cluster Manager.
If you have encountered a similar issue or have experienced problems caused by default settings in a wizard, it’s important to be aware of this potential pitfall. Always double-check the settings and options presented to you during the configuration process to ensure they align with your specific requirements.
By taking the time to review and adjust the default settings, you can avoid unnecessary complications and ensure a smooth and successful configuration of your SQL Server cluster.
Have you ever run into a similar issue where default settings in a wizard caused problems? Share your experiences in the comments below!