Re: Windows 2000 cluster drives

From: Mike Rosado [MSFT] (mikeros_at_online.microsoft.com)
Date: 03/09/05


Date: Tue, 8 Mar 2005 22:06:37 -0600

Scott,

Don't use Disk Manager in Computer Management to determine if the disk came
Online on the other node or not.. Because if you are viewing the node via TS
session, it may not refresh correctly.

Test the failover like from node A to node B, once failover has settled down
after the move to node B then open Windows Explorer on node B and see if you
can access the disk that are on that node. Make sure to check the Cluster
Logs and System Event Logs on both nodes for any errors after the failover.
What is the exact verbatim of the error?

-- 
Thanks in advance,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
<http://www.microsoft.com/info/cpyright.htm>
-----Original Message-----
"Scott" <Scott@discussions.microsoft.com> wrote in message
news:73FBCAEE-D656-4F43-9B51-2041D3438ED8@microsoft.com...
> The cluster is setup and one node can has ownership of the drives, I can
see
> the drive letters in My Computer and if I go into disk management.  The
other
> node does not see these drives at that time in MY Computer or Disk
> Management, which is way it should since it is not the active node.  I
then
> fail over the cluster and in the cluster management everything fails over
> just fine and no errors in the event log.  I then go to the node that is
now
> the active node, it shows the drives in Computer management, but when I go
to
> My computer it does not show the drives.  In computer management I try to
> open the drives there and recieve an error that says it is not able to
access
> it.  I have tried several different ways and found out that I can repeat
this
> same action on the other node as well, so it is not just one machine it is
> something within the access of the drives and the cluster.
>
> "Mike Rosado [MSFT]" wrote:
>
> > Scott,
> >
> > I'm a little confused.  You stated that everything regarding Cluster on
both
> > nodes installed fine and failover fine.  Then you state that everything
> > works fine on one node, but not on the other.
> >
> > Both nodes are not suppose to write to the SAN, unless you have several
> > virtual groups in which one group is active on one node while the other
> > group is active on the other node making it an Active/Active Cluster.
So
> > each group would be owner of a particular Physical Disk resource on each
> > node.
> >
> > If this is not the case, then please provide a lot more details of the
> > events in the System Event Log and errors experienced in the Cluster Log
> > when you experience the problem.
> >
> > MSCS Cluster service is shared-nothing cluster model, all servers or
cluster
> > nodes in the cluster can own the shared cluster resources. However, only
one
> > node may own and manage these resources at any one time. This means that
> > while cluster node A owns a physical disk, no other cluster node can
access
> > it. Node A has exclusive ownership of this shared disk until it is
either
> > manually moved to another cluster node, or until node A fails and
another
> > cluster node assumes ownership of the resource.
> >
> > In Windows Server 2003, it's a little bit more robust in managing the
disk
> > subsystem.  See the following article for more details:
> >
> > 818878 Managing Disk Ownership in a Windows Server 2003 Cluster
> > http://support.microsoft.com/?id=818878
> >
> > -- 
> > Hope this helps,
> > Mike Rosado
> > Windows 2000 MCSE + MCDBA
> > Microsoft Enterprise Platform Support
> > Windows NT/2000/2003 Cluster Technologies
> >
> > ====================================================
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> > ====================================================
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > <http://www.microsoft.com/info/cpyright.htm>
> >
> > -----Original Message-----
> >
> > "Scott" <Scott@discussions.microsoft.com> wrote in message
> > news:13ED7773-BF81-42DF-9000-098A6ED6205D@microsoft.com...
> > > I have installed Cluster on two nodes.  Everything seems to work fails
> > over
> > > properly and in disk management the drives show up that are attached
to
> > the
> > > SAN.  If I go to My Computer the drives do not show up.  Everything
works
> > > fine
> > > on one node but not on the other. I can get both nodes to write to SAN
> > > drives but I have to reboot.  Is the cluster access corrupted, if so
can I
> > > uninstall the cluster and reinstall it?
> > >
> > > Any help is appreciated.
> > >
> > > Scott
> > >
> >
> >
> >


Relevant Pages

  • Re: Correcting corrupt $MFT on shared clustered disk.
    ... against a cluster disk. ... handles against the disk. ... After digging into it I figured out I didn't need the extended maintenance mode and figured out the rest of the article. ... If I assign drives for different areas, I figure we'll eventually end up with the same problem we had before: some areas running out of space and others with space to spare. ...
    (microsoft.public.windows.server.clustering)
  • Re: Correcting a corrupted $MFT on a shared clustered disk
    ... Also, the problem I'm having is on the smaller basic disk, the GPT one is ... When I do run chkdsk, are there any special issues with the cluster? ... The three drives are a 500MB for the quorum, ...
    (microsoft.public.windows.server.general)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... Isin't the W2K3 Cluster Server Recovery tool designed to ... > 4) assume the Old disk drive is O: and the New disk Drive is N: ... > 4) Create a new Disk Resource for the new disk and have that in the SQL ... >>just fine but not the data drives, basically on step 14 my old drives ...
    (microsoft.public.windows.server.clustering)
  • Re: Correcting a corrupted $MFT on a shared clustered disk
    ... Phase 1 went through pretty fast, it found and corrected the 60 or so corrupted attribute & orphaned records that the read-only chkdsk passes were detecting. ... Also, the problem I'm having is on the smaller basic disk, the GPT one is ... are there any special issues with the cluster? ... The three drives are a 500MB for the quorum,> and two ...
    (microsoft.public.windows.server.general)
  • Re: Correcting a corrupted $MFT on a shared clustered disk
    ... Also, the problem I'm having is on the smaller basic disk, the GPT one is ... for the CHKDSK, or is it something that's only going to get worse? ... are there any special issues with the cluster? ... The three drives are a 500MB for the quorum, ...
    (microsoft.public.windows.server.general)