I am trying to move my pubs and northwind log files to a different shared disk on a clustered system (because I have data and logs separated). I am trying to do this via detach and attach db. I can detach the db just fine. However, When I try to copy the .ldf file to its new drive location I get an operating system error similar to: Cannot access device. The device does not exist.
I cannot see the drive in Windows Explorer, but the drive does exist in SQL server because my other log files are on that disk device. I can run a dir command from cmdshell in QA and look at them as well. This shared disk device is in the SQL Group in the Cluster Administrator. Why does the cluster administrator and the Query Analyzer recognize the drive but the operating system does not?
I cannot even do a Start | Run | <drive letter
Thanks for any smart Guru help.............

--techgirl

Sometimes W2K cannot see new clustered disks in Explorer (even after a Disk Manager rescan) even though the cluster service can. Rebooting all nodes of the cluster often fixes the problem (but I guess you've already tried that...).

Thank you Stephen, I did try rebooting several times yesterday to no avail. However, as it stands this morning, the drives are magically back. Go figure.................

--TechGir

----- Stephen Strong wrote: ----

Sometimes W2K cannot see new clustered disks in Explorer (even after a Disk Manager rescan) even though the cluster service can. Rebooting all nodes of the cluster often fixes the problem (but I guess you've already tried that...).

Hi,

To add on this, depending on your hardware, only one node will be able to
see your shared storage. This node must be the owner of the Disk ressource
to be able to access the disk (in explorer, etc). Make sure you are doing
your work on the correct node (by checking with Cluster Administrator who is
currently owning the ressource). At least, that's how our cluster works
here.

HTH.

"TechGirl" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Go figure..................
nodes of the cluster often fixes the problem (but I guess you've already
tried that...).

We've experienced problems when presenting new disks to W2K MCS where cluster services (on the node owning the disk) can see the disk but Explorer cannot. It's not a SQL issue but a general MCS issue. Reboots generally fix it (not sure why).

If you are using Terminal Server to access Explorer on the node, that could
be your problem. It only knows about the drives that were there at the time
the Term Serv connection was made.

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.