July 31, 2010 at 3:57 am
We are getting the following error during SQL-2008 installation on a cluster node (active node) in an active-active-passive cluster configuration. We are using mount points in our implementation to increase the number of individual volumes that will host the database files. This occurs in the Cluster Disk Selection phase:
The mount point disk volume '\\?\Volume{fdba841d-9c06-11df-b213-0017a4770490}\' mounted at 'I:\$RECYCLE.BIN\S-1-5-21-1214440339-854245398-1801674531-11362\$RXP8E68\' is not a clustered resource.To continue, add the resource to the cluster, or remove the mount point to cluster the shared disk.
Anyone have any ideas how to resolve this?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
July 31, 2010 at 9:44 am
I am not sure about the reference to the recycle bin in the error - that seems a bit suspicious.
Is the I:\ drive a cluster resource? Is the mount point setup as a clustered resource and available to all nodes in the cluster?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
July 31, 2010 at 9:53 am
Jeffrey Williams-493691 (7/31/2010)
I am not sure about the reference to the recycle bin in the error - that seems a bit suspicious.Is the I:\ drive a cluster resource? Is the mount point setup as a clustered resource and available to all nodes in the cluster?
Yes, I think the answer is yes to both questions. I didn't set it up myself, it was set up by our system administrator and SAN specialist. Is there any test I can run - perhaps using the Failover Cluster Manager tool - to confirm this?
Thank you for any hints on this, I'm new to the cluster implementation.
July 31, 2010 at 10:40 am
You can validate it yourself with minimal effort - RDP to the server and use the cluster administrator console (is this windows 2008 also, or 2003?). The administration of clusters had changed in windows 2008 and I'm not familiar with it yet.
What you want to do is validate that the drive has been added to the same resource group as SQL Server and that SQL Server is dependent upon that drive.
As for validating that the mount point is added to all nodes - you need to follow up with the SAN guys on that.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
December 20, 2011 at 8:22 am
Just FYI, I was experiencing the same error along with another error in this post that seem to be correlated. I posted the solution there.
Long story short, we ended up having to format the drive that housed the mount points then recreate them and that cleared up the issue.
December 20, 2011 at 11:02 am
January 3, 2012 at 8:19 am
Just check that the drive you are selecting for install should be in cluster and should not have any dependencies.
February 26, 2014 at 4:21 am
For anyone else reading this in the future, this may have happened if someone had deleted a mounted folder through Windows Explorer, which by default could have moved the mount point to the Recycle Bin. This would then make the install fail if the disk holding the mount point was selected during the install and the mount point under the Recycle Bin wasn't configured as a clustered resource.
If this was the problem, emptying the mount point folder from the Recycle Bin should resolve it.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply