What you'll want to do is this:1. Remove the dependencies on the disks that you moving between.2. Remove the cluster resources from Cluster Administrator completely.3. Re-create the cluster resource that you are moving to.4. Bring the "new" resource online (resource created in step 4).5. Make SQL Server dependent on that resource.6. Bring SQL back online.

I've had issues in the past where I had a cluster resource created, I added a new disk and tried to re-use a letter and use the existing cluster resource that was attached to that letter, and it didn't like that. After that experience, I always completely remove the cluster resources and re-create them after my work within the "Disk Management" section of Computer Management.

The reason you can start SQL within the command line utility is because the server must be seeing the correct drives, but the cluster isn't. It can't hurt to re-create the resources.

As this is quite an old thread I expect you've got your cluster issue sorted now (or given up ), but I've recently been doing the same thing.I didn't need to take the drastic steps that SK recommends - there's no need - but you need to make sure that when you start SQL Server in master-recovery mode (using the /f and /T3068 parameters), you run an ALTER DATABASE command to logically MOVE the mssqlsystemresource data and log files to the new location and then physically move the files.

You should then be able be able to change the startup parameters in SQL Server Configuration manager and restart the SQL Server Service via Cluster Administrator. If that doesn't work, copy the master and mssqlsystemresource data and log files back to their original location, start SQL Server (via Cluster Admin), make the changes again, shut down SQL Server (again via Cluster Admin) and restart. The new startup parameters should then be picked up.

This problem is caused by Registry entries on the cluster getting out of synch with the startup parameters. I can testify that it can be a complete pain!

I have this same issue, can't figure out why Sql Server does not have this documented.2 node Sql Server 2005 64 bit enterprise.I have moved all databases without issue using:[url=http://msdn.microsoft.com/en-us/library/ms345408%28SQL.90%29.aspx][/url]

Now I could not connect using this method for a cluster setup. It works moving master and resource when not clustered. I was getting connection errors when attempting to move the resource using sqlcmd an the net start service part. So I found this and other links in this forum. I seems to be the closest to reality that I can find.

So here is my steps that I will attempt for this cluster to move master and resource databases: