Win 2003 Enterprise Edition Cluster physical disk not cluster capa

Discussion in 'Windows Server' started by Steve, Oct 25, 2005.

  1. Steve

    Steve Guest

    I have a set of identical IBM xSeries 232 servers (I already looked they are
    on the HCL) I installed all the latest firmware, BIOS and windows updates and
    installed and configured active directory, dns and dhcp. I then attemped to
    run the Cluster Administration to start a new cluster. I didn't get any error
    messages until the last screen where every thing else checks out ok except
    for the following.

    The physical disk "Disk C" is not cluster-capable
    The physical disk "Disk E" is not cluster-capable
    The physical disk "Disk F" is not cluster-capable

    Here is how I have the disks configured:
    Disk 0 Basic 16.96 GB NTFS Healthy (system) (C:)
    Disk 1 Basic 33.90 GB NTFS Healthy (E:)
    Disk 2 Basic 68.36 GB NTFS Healthy (F:)

    If you want the log from the "New Server Cluster Wizard" I would be glad to
    post it if it will help out.

    Any Help Would Be Greatly Appreciated.

    Steve, Oct 25, 2005
    1. Advertisements

  2. You have not mentioned how Disk C, E, and F are attached. Are these local

    In order for create a cluster (except for a 1 node cluster, which is a
    fairly specialized animal) the disk volumes must be attached to (and
    accessable by) both servers in some physical manner, (such a via a SAN, a
    shared SCSI storage unit of some type, etc...)

    - MEK
    Michael Kohlman, Oct 26, 2005
    1. Advertisements

  3. Steve

    Steve Guest

    I was told by a MS tech that it was not necessary to have a shared san. The
    disks are local and I was going to share the D drive which contained the
    quorum. I can setup a san that both the servers can connect to if it is

    Thanks For your help
    Steve, Oct 26, 2005
  4. Not sure where the confusion is coming from, but the only disks that you
    will be able to use for clustering will need to be physically shared disks.
    Currently we run around a dozen Windows 2003 cluster nodes (Exchange, SQL,
    and File Servers). While the actual O/S is loaded onto a local disk
    (typically a RAID 1 mirror) all of the volumes that are intended to be used
    for clustering are LUNs attached to a Dell/EMC SAN. Otherwise there is no
    way for one of the cluster nodes to assume control for the disks and
    resources when a node fails.

    Using a SAN is probably the easiest/best way to set up clusters. While it
    is possible to use a SCSI disk array with two interfaces (one attached to
    each node) I've personally never seen one that was very reliable when a
    failover occured (which kind of defeats the whole purpose). iSCSI is now
    supported with SP1 but I've had no heavy experience with that as of yet.

    A good place to start for information on how to do this is here:

    A Great Doc from Microsoft on how to set up clusters can be had here:

    - MEK
    Michael Kohlman, Oct 26, 2005
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.