Re: Cluster (only physical disks) wont move to another mode



Take cluster out of the picture and verify that both servers can see
the disks. Make sure that both servers are not up at the same time
with cluster disk driver diabled, otherwise you risk file system
corruption.

This is an example of some steps used to verify that the second node
could see a Q drive. Same steps apply to your effort. Sounds like a
SAN configuration issue to me.



**Important
Only one node that is in the cluster must be running to prevent disk
corruption!

Therefore, before you use this method, shut down all the other nodes
that are in the cluster.

(Per our discussion, Node 2 was the node which could not see Q: drive
via Disk Management.)

During an outage window, gracefully shutdown the working node, Node 1.
On Node 2, click Start, point to Administrative Tools, click Computer
Management, and then click Device Manager. Click view show hidden
devices.
Expand Non-Plug and Play Drivers, right-click Cluster Disk Driver,
click Properties, click the Driver tab, in the Startup type list click
Disabled, and then click OK.
Go to services and set startup type for Cluster Service as Manual.
Quit Computer Management, and then restart your computer Node 2, Node 1
should remain turned off.
At this point, Cluster is completely disabled and out of the equation,
via disk management, all drives should be visible including Disk Q.
If Disk Q is not visible in disk management, hardware vendor and SAN
administrator needs to correct issue.
Once Node 2 can see Disk Q, reverse steps to re-enable cluster service.

Click Start, point to Administrative Tools, click Computer Management,
and then click Device Manager. Click view show hidden devices.
Expand Non-Plug and Play Drivers, right-click Cluster Disk Driver,
click Properties, click the Driver tab, click System in the Startup
type list, and then click OK.
Set startup type for Cluster service as automatic.
Quit Computer Management, and then restart your computer.
Cluster service should start and you should be able to browse the Q
drive since Cluster disk driver has provided access to Node2 and it
owner of the Quorum.
Once verified. Power up Node 1; verify that all resource groups can be
failed back and forth between nodes.

Dave

.



Relevant Pages

  • SUMMARY: changed WWID on cluster member boot disk
    ... disk and quorum disk of a single-member cluster, ... I could no longer boot from the cluster disks, ... the pre-cluster stand-alone system disk; ... the root1_domain on LUN containing the member boot disk was found ...
    (Tru64-UNIX-Managers)
  • Re: Windows 2000 cluster drives
    ... Don't use Disk Manager in Computer Management to determine if the disk came ... Windows NT/2000/2003 Cluster Technologies ... > node does not see these drives at that time in MY Computer or Disk ...
    (microsoft.public.windows.server.clustering)
  • Join an existing cluster
    ... I had a cluster setup with 2 computers running windows ... shared disk array. ... Creating a dummy Local Quorum resource. ... on the same storage bus as the boot disk... ...
    (microsoft.public.windows.server.clustering)
  • Re: Creating a wide area VMS Cluster
    ... > My goal is to provide a disaster tolerant cluster for both OS and data. ... disrupting the balance of the effect of votes between sites A and B. ... You have the option of a single shadowed system disk between the ...
    (comp.os.vms)
  • RE: Cluster IP Address Does not fail over
    ... The cluster IP has no dependicies at all. ... Node1 disk manager sees LUN5. ... [DiskArb] ...
    (microsoft.public.windows.server.clustering)