Drives not showing up/dependencies error

[cmwright]

Hi all,

I just installed a new instance of SQL Server 2000 Enterprise Edition on a 2-node cluster. The server has 3 local drives and several SANS drives that have been presented to the server. Everything is working quite well, with 2 exceptions.

1. When I try to create a maintenance plan, 2 of the drives presented to the server (SANS drives) are not showing up for me. So, some SANS drives show up, and some do not. Any ideas as to why?

2. When I try to move the tempdb to drive R (actual path/fileName changed to protect the innocent), I get this error:

Server: Msg 5184, Level 16, State 1, Line 3
Cannot use file 'r:\myPath\myFile.mdf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used.

Server: Msg 5184, Level 16, State 1, Line 2
Cannot use file 's:\myPath\myFile.ldf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used.

Microsoft provides the following help:

http://support.microsoft.com/kb/295732

I tried that, and it did not work.

Many thanks for any insight you can provide.

-Chris

 

[ptheriault]

is your disk configures as dynamic drives?


- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[cmwright]

Nope. They are all basic. Interestingly enough, I can type in the path and it works fine. The drives are just not visible in the Maintenance Plan screen for backup location. I even created a plan and tested just now, so it's simply not showing up in the choice list.

I can live with that, though I'd like to understand how to fix it. Thanks!

The TEMPDB move is now my main concern.

-Chris

 

[ptheriault]

Maybe you just need to restart your SQL Agent?

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[cmwright]

I tried that. I also added these drives as dependencies in the SQL Server cluster resources. Some that are in there show in the Maintenance Plan wizard, some do not.

Very odd, and I am sure that it has something to do with network setup (AD and such), but I don't want to get into the finger-pointing game.

Thanks for helping me. I appreciate the suggestions.

-Chris

 

[ptheriault]

np

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[cmwright]

Any ideas on the second issue? The dependency thing?

-Chris

 

[ptheriault]

It looks like those drives are not part of the cluster. What are your shared drives in the cluster manager?

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[cmwright]

They are definitely part of the cluster. The MS KB said that for SQL Server to use them, the SQL resource had to list them as dependencies. They do show up in the available list of dependent drives, and appear to add just fine as dependencies. However, the script to swith the tempdb over still kicks the error. Shared drives are c-j, q, and r in the cluser resources.

-Chris

 

[ptheriault]

hmm, I'm not sure I know what could cause that then..sorry. Denny might know.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[cmwright]

Solution for drives not showing:

I indicated that I had placed all drives necessary as dependencies. I also had restarted the service. That didn't help.

However, I decided to fail over the cluster and then back again. That worked. All drives showed up. I don't know why that's different necessarily than stopping and restarting, but that's what did the trick.

Still working on the tempdb issue.

-Chris

 

[cmwright]

Problems solved!

Failing over the cluster and back fixed both problems.

Thanks for everything!

-Chris