Windows server 2008 doesnt like the shared disks for the quarm and application drive


I'm trying to set up a print server cluster in ESX.  The servers are Windows 2008 Ent. and on separate ESX hosts.  I have both of the shared disks for the quarm and application added and visible on both servers  but when I try to add the quarm or application disk to the windows cluster it says that there are not any disks available.  It alos says this when I run the clustering configuration tests. Both of the shared disk are RAW luns presented to both servers in physical compatibility mode and the both the OS drives are VMDKs that have been created using the thick disk option.  Does anyone have any ideas on why it doesnt like the disks or what can be done to correct this issue?
Who is Participating?
asrdiasConnect With a Mentor Commented:
From other expert exchange post:

iSCSI, FC and SAS are support on Windows Server 2008
so if you want to setup Windows Server 2008 Clustering on ESX you have to present the LUN directy to the guest by using iSCSI or using NPIV...."

The post :

shutdown one of the Windows 2008 servers and try to create the cluster on the other... what happens ?
SeasultAuthor Commented:
Same results.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Ok... I read it wrong.
You say the disks are Raw. Keep one of the nodes off and with the other go to disk manager and initialize the disk and create an NTFS partition puls a drive letter. Lets imagine Q: for the Quorum and P: for the application disk.
Goto to the explorer and make sure the disks are visible as drive letters. Try now....
SeasultAuthor Commented:
It still doesnt like the disks.  I have even tried a one node cluster.... 2008 just doesnt like the raw disks.  I think I'm hitting the bleeding edge of vmware.
In order to form the cluster Windows needs the disks to contain a supported file system and drive letter. Is not a matter of taste, is just the way it is.
This happens because windows needs to put files on the Quorum disk in order to start the cluster service (the cluster log) and also needs to sign the disks to mark them as cluster shared disks. (among other things)
Raw disks ??? No way !!!

Here's more details:

Storage: You must use shared storage that is compatible with Windows Server 2008.
For a two-node failover cluster, the storage should contain at least two separate volumes (LUNs), configured at the hardware level. One volume will function as the witness disk (described in the next paragraph). One volume will contain the files that are being shared to users. Storage requirements include the following:
"      To use the native disk support included in failover clustering, use basic disks, not dynamic disks.
"      We recommend that you format the partitions with NTFS (for the witness disk, the partition must be NTFS).
"      For the partition style of the disk, you can use either master boot record (MBR) or GUID partition table (GPT).
The witness disk is a disk in the cluster storage that is designated to hold a copy of the cluster configuration database. (A witness disk is part of some, not all, quorum configurations.) For this two-node cluster, the quorum configuration will be Node and Disk Majority, the default for a cluster with an even number of nodes. Node and Disk Majority means that the nodes and the witness disk each contain copies of the cluster configuration, and the cluster has quorum as long as a majority (two out of three) of these copies are available.
SeasultAuthor Commented:

Thank you for your comments.

When I was referring to raw disks I was referring to a VMware term meaning that it is a actual physical disk as opposed to VMDK (or Virtual Had Drive).

The quarm disk and the application disk are both formatted in NTFS and have a drive letter assigned to them.
A ok ! Sorry for the missunderstanding...

If Vmware is presenting the disks as connected to a virtual SCSI adapter that emulates a Parallel SCSI-2 type controller then Windows 2008 does not support this....
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.