Re: pbl with a w2K server attached to a IBM ESS (SAN)

Remember that MSCS is a "Shared-Nothing" model - the LUNs will only be
accessible from one node at a time...Make sure you've completed all the
necessary steps on the first node and all existing LUNs before beginning to
add additional nodes...

Checklist: Installing a Physical Disk resource
http://technet2.microsoft.com/WindowsServer/en/Library/0c0bd64b-6902-4ae7-aa91-a43c93b9fd4b1033.mspx

To connect the shared storage buses and assign drive letters
1.
Install Windows Server 2003, Enterprise Edition or Windows Server 2003,
Datacenter Edition on all nodes.

Caution

. All nodes in a cluster must be running the same version of the
operating system, that is, either Windows Server 2003, Enterprise Edition or
Windows Server 2003, Datacenter Edition. You cannot run both Windows Server
2003, Enterprise Edition and Windows Server 2003, Datacenter Edition on
nodes in the same cluster.


2.
Prepare the controllers for the shared storage bus, following the
instructions in your storage bus owner's manual.

3.
Install the controllers for the shared storage bus, but do not connect
them to the shared storage bus.

4.
Connect the shared storage devices to the shared buses, and then
connect the shared storage buses to all nodes.

5.
Start the operating system on the first node on which you intend to
create the cluster.

6.
Format the disks on the cluster storage device as NTFS.

Caution

. Each disk on the cluster storage device must be a basic disk,
not a dynamic disk.


7.
Partition the disks on the cluster storage device.



8.
Do one of the following:

. Assign drive letters to the disks on the cluster storage
device.

. Assign mount points to the disks on the cluster storage
device.




Caution

. Make sure that you create unique mounted drives so that they
do not conflict with existing local drives on any node in the cluster.

. Do not create mounted drives between disks on the cluster
storage device (cluster disks) and local disks.

. Do not create a mounted drive from a clustered disk to the
cluster disk that contains the quorum resource (the quorum disk). You can,
however, create a mounted drive from the quorum disk to a clustered disk.

. Mounted drives from one cluster disk to another must be in the
same cluster resource group, and must be dependent on the root disk.


9.
Label all partitions to match their drive letters or mount points
assigned in the step above.

10.
Use Cluster Administrator to add the first node to the cluster.

Caution

. Completely create the cluster on one node before you join
additional nodes to the cluster.


Important

. When you create a cluster, Physical Disk resources will be
automatically created for cluster disks that use drive letters. However, if
your cluster disks use mount points, Physical Disk resources will not be
automatically created for those disks; you must manually create disk
resources for cluster disks that use mount points.


11.
Join one or more additional nodes to the cluster.





Hope this helps,
--Ryan

--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP

"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."

This posting is provided "AS IS" with no warranties, and confers no rights.

"Eric" <eboucq@xxxxxxxx> wrote in message
news:jd6u025mslf7jiloq9dgr703pge7gqgsjl@xxxxxxxxxx
Hi,

One of the node of my cluster doesn't see anymore the LUNS allocated
formy cluster. These LUNs are in an IBM ESS storage (SAN)
In the device manager, I can see the physical drives but not in the
Disk Management.
In fact, the only 2 LUNs I see in the Disk Management are unallocated
LUNS.
I don't have any problem with the second node.
There must be something wrong in the registry but I don't know where
to look.
Any idea please ?

Thanks.
Regards.
Eric.


.

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)
  • 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: 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: 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)
Quantcast