No Disks suitable for cluster disks on Windows 2012 R2 Cluster

Hi guys,

I am facing a problem with Microsoft Cluster on Windows Server 2012 R2.
I will explain in steps:
- I had a Windows 2008 R2 cluster running Hyper-V;
- In this cluster, I have some disks presented by an iSCSI Dell storage;
- After the upgrade of servers to Windows 2012 R2, some disks cannot be recognized by cluster (when I try to add disks I receive the following message: No Disks suitable for cluster disks), in storage system nothing was changed, some disks (directly mapped to Red Hat virtual machines in a Passthrough  mode) can't be added to cluster. The interesting fact that on Windows 2008 I presented these disks before without any problem, in the same way with Red Hat filesystem present.
- In the Windows Disk Management on each server I can see the disks and bring them online if I want (to workarround this problem I started VM machines outside the cluster on one node);
- I ran the cluster validation report before;
-
I am very concerned about this issue.

Any idea to help me?
MicronasAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Your previous iSCSI connected disks were set up in a CSV?
MicronasAuthor Commented:
Hi Philip,

No, the previous cluster (Windows 2008 R2) didn't use CSV. Now the new cluster it doesn't use CSV too.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
What kind of cluster are we talking about here? We build Hyper-V and Scale-Out File Services clusters and CSV is where all storage ends up but witness/quorum.
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

MicronasAuthor Commented:
We are talking about Failover cluster, the virtual machines (vhd) are pointed to units (in this case F and G that are iSCSI drives).
In this specific case, I have 2 Red Hat VM's that are pointed to direct disks, in this case I need that these disks are present in cluster.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
In a Hyper-V cluster setting iSCSI storage is attached to all HV nodes in the cluster.

That storage in turn is a part of the Cluster Validation Wizard process (this was run right?).

Once CVW and then the cluster is stood up the now available Cluster Storage would be added to Cluster Shared Volumes.

Once into CSV your VHD(x) files would be hooked into the Highly Available (HA) VMs via C:\ClusterStorage\VolumeXX\VMName.VHDX.

You can create one large LUN to be set up as a CSV, or two so that both controllers in storage share 50% of the load thus ending up with two CSVs. Or, one can set up a dedicated LUN/CSV for each set of VHDX files for VMs.

That's how it's done.
MicronasAuthor Commented:
Philip,

That diks have an EXT3 filesystem, they was presented to old cluster (Windows 2008 R2) direct to virtual machines (passthrough).
So, after I installed windows 2012 r2, in the same cluster scheme (same hardware, same settings), simply the disks can't be added to cluster.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
We've not used pass through disks in years and then only for external storage to hook into a VM for a restore.

Hook the iSCSI target into all nodes in the cluster. Make sure to set them to OFFLINE in Disk Management on all nodes.

From there, hook the now OFFLINE disk into the VM via Hyper-V Manager on the node that currently owns the VM. Make sure it is set to IDE channel 0.

Boot the VM.

The catch will be if the VM will Live Migrate or fail over to another node. I think it should as we have used iSCSI targets in the past as backup destinations for VMs in a cluster.

That's probably the best way that I can think of to get this done.
MicronasAuthor Commented:
Hi Philip,

I did this, all the cluster nodes (in this case only two) the disks are Offline (in computer management snap-in). The cluster still continue showing the message "No Disks suitable for cluster".
An interesting fact that I have 5 disks in the same storage system, but only 3 can't be attached. The settings on Storage system are the same (before migration from Windows 2008 R2 to Windows 2012 R2). These disks are EXT3 partitions, but one of the imported disks (present in cluster) is EXT3.

Any new ideas?
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Because the disks are not NTFS.

When the disk is OFFLINE you should be able to hook that disk into the VM within Failover Cluster Manager or via Hyper-V Management on the owner node.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MicronasAuthor Commented:
I'm not sure about this, because one disk is EXT3 and was imported without any problem. But I will try to simulate this problem in my environment. I will try with EXT3 disks.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
How the disks are formatted should be immaterial.

Once the disks are set to OFFLINE in Disk Management on all nodes they can be passed through directly to the VM via Hyper-V Manager. Since they are network located there should be no issues with failover if there is a need.
MicronasAuthor Commented:
Hello Philip,

I found some error messages in Diagnostics of Cluster, some messages like this: "Disk 2: Unknow patition type, ignoring".
So, this disk is one of that I can't import. Today I will move the data on this disk (EXT3) to a VHDX file using some image software.
I will provide more details soon, but I believe that you is right, the problem is the partition type.

Thank you!
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
You're welcome.
MicronasAuthor Commented:
Hi Philip,

in fact the problem was partition type.

Thank you!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.