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.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jmachado81Author Commented:
And these storage disks are all listed under the resources of our SQL Server role and the status is Online.
Jason clarkDBA FreelancerCommented:
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ãoMSSQL Senior EngineerCommented:
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?
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

jmachado81Author Commented:
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...
jmachado81Author Commented:
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.
Vitor MontalvãoMSSQL Senior EngineerCommented:
Your disk dependency is a File Server?
Anyway, I can't see that SQL Server is depending on the MountPoint resource.
jmachado81Author Commented:
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?
Vitor MontalvãoMSSQL Senior EngineerCommented:
Should we add that S:\ or Mount_Point drive as a dependency of the SQL Server?
This one for sure otherwise the SQL Server instance won't recognize it.

Are there any other primary dependencies we should review?
Just confirm that you have the IP Address, Network name and necessary disk resources (Data, log, tempdb, system dbs, backup).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jmachado81Author Commented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.