Umar,

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.

Best of luck,

SK