Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Mount-point related error during SQL installation on cluster node Expand / Collapse
Author
Message
Posted Saturday, July 31, 2010 3:57 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, April 17, 2014 2:42 PM
Points: 1,851, Visits: 3,575
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?


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #961716
Posted Saturday, July 31, 2010 9:44 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Thursday, April 17, 2014 11:17 AM
Points: 4,379, Visits: 9,470
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 opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs
Post #961766
Posted Saturday, July 31, 2010 9:53 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, January 23, 2012 12:02 PM
Points: 13, 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.
Post #961767
Posted Saturday, July 31, 2010 10:40 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Thursday, April 17, 2014 11:17 AM
Points: 4,379, Visits: 9,470
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 opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs
Post #961772
Posted Tuesday, December 20, 2011 8:22 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, April 04, 2014 9:05 AM
Points: 336, Visits: 766
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.
Post #1224464
Posted Tuesday, December 20, 2011 11:02 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 11:51 AM
Points: 5,958, Visits: 12,839
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"
Post #1224647
Posted Tuesday, January 03, 2012 8:19 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, February 27, 2014 1:33 PM
Points: 192, Visits: 186
Just check that the drive you are selecting for install should be in cluster and should not have any dependencies.
Post #1229302
Posted Wednesday, February 26, 2014 4:21 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, April 08, 2014 1:31 AM
Points: 2, Visits: 181
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.
Post #1545322
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse