Avatar of jmachado81
jmachado81
 asked on

SQL 2012 clustering

We have a pair of 2012 R2 servers clustered together with SQL 2012.  Recently when we attempt to attach a database and associated log file we get the attached error.  We are unaware of or even if any changes were made to this cluster, and there are no current cluster errors displayed.

We have found multiple articles stating this is a dependency issue but we are unsure where this dependency is missing?  SQL Server resource, Agent resource, disk resource, or all the above.  

We are going to failover the cluster to see if the behavior persists on the other node but I was hoping others had recommendations as to what this can be.
Capture.PNG
Microsoft SQL Server* Clustering

Avatar of undefined
Last Comment
jmachado81

8/22/2022 - Mon
jmachado81

ASKER
And these storage disks are all listed under the resources of our SQL Server role and the status is Online.
Jason clark

this error genrally occur when drive is not having dependency with the SQL Server resource. Check this,
Add the dependency at the SQL Server resource under SQL Group.
While adding dependency SQL Server resource must be offline.
Once add bring online and now this will work.

have a look here: https://blog.sqlauthority.com/2016/12/13/sql-server-error-cluster-patching-error-5184-severity-16-state-2/
Vitor Montalvão

And these storage disks are all listed under the resources of our SQL Server role and the status is Online.
Can you post a screenshot with those dependencies listed?
Your help has saved me hundreds of hours of internet surfing.
fblack61
jmachado81

ASKER
Well the failover last night went miserable but we may have found the issue or one of them.  It appears that even though each node had the below local drives, somehow the I:\ became a shared clustered disk.  We did not view the I:\ drive in the cluster resources, however when i viewed the disk attributes it stated it was a clustered disk and it also stated that it was reserved in the disk management.

C:\ OS
I:\ sql installation files
P:\ pagefile

After one of the nodes were evicted we were able to clear disk attributes on both nodes so the I:\ was back online.  I think we are going to try to readd this node back to the cluster later.

How can a disk become a clustered disk if not part of the cluster resources?  We don't know how this came to pass...
jmachado81

ASKER
It appears that even though the cluster is back online we still cannot add databases to the cluster (of one).  I have attached the screenshot of our SQL Server (other resources) dependency and our storage dependency.  All of our databases and log files are stored in their own volumes on an S:\ which is called "Mount_Point" which you can view in the screenshot, and they all have the same dependency.  The top-level S:\ drive or Mount_Points has no dependencies listed...only the LUNs (sub-directories holding mdf/ldf files) mounted to this drive have dependencies.
sqlserver_depend.PNG
Disk_depend.PNG
Vitor Montalvão

Your disk dependency is a File Server?
Anyway, I can't see that SQL Server is depending on the MountPoint resource.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
jmachado81

ASKER
The cluster has a File Server resource installed and its not pointing to a typical file server.  Should we add that S:\ or Mount_Point drive as a dependency of the SQL Server?  Are there any other primary dependencies we should review?
ASKER CERTIFIED SOLUTION
Vitor Montalvão

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
jmachado81

ASKER
Thanks for your assistance.  In additional to adding that top level drive, we also added each drive in which an mdf/ldf file was located as a dependency.  These resolved the errors in attaching a database to the server.