SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Mount-point related error during SQL installation on cluster node


Mount-point related error during SQL installation on cluster node

Author
Message
Marios Philippopoulos
Marios Philippopoulos
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4474 Visits: 3754
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
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
Jeffrey Williams 3188
Jeffrey Williams 3188
SSCertifiable
SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)

Group: General Forum Members
Points: 7633 Visits: 9966
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
Problems are opportunities brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs

mphilippopoulos
mphilippopoulos
SSC Rookie
SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)

Group: General Forum Members
Points: 49 Visits: 104
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.
Jeffrey Williams 3188
Jeffrey Williams 3188
SSCertifiable
SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)

Group: General Forum Members
Points: 7633 Visits: 9966
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
Problems are opportunities brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs

JohnnyDBA
JohnnyDBA
Say Hey Kid
Say Hey Kid (702 reputation)Say Hey Kid (702 reputation)Say Hey Kid (702 reputation)Say Hey Kid (702 reputation)Say Hey Kid (702 reputation)Say Hey Kid (702 reputation)Say Hey Kid (702 reputation)Say Hey Kid (702 reputation)

Group: General Forum Members
Points: 702 Visits: 897
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.
Perry Whittle
Perry Whittle
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19728 Visits: 17239
as already mentioned, see my article at this link for more info on setting up and using mount points for SQL Server

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
hkamal.infoedge
hkamal.infoedge
SSC Veteran
SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)SSC Veteran (218 reputation)

Group: General Forum Members
Points: 218 Visits: 311
Just check that the drive you are selecting for install should be in cluster and should not have any dependencies.
james-508023
james-508023
Grasshopper
Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)

Group: General Forum Members
Points: 20 Visits: 313
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search