Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, December 21, 2011 7:40 AM
I'm attempting to setup Failover Clustering for the first time and I'm receiving the following error.
**There are no available disks in the cluster.
**
I've searched a bit and keep coming across blogs about how to setup the cluster, but not much on this error message. Under storage I see my NTFS volume I created on the SAN, and it's online. I've also enabled the Cluster Shared Volume option. I've created a second storage too, one for my quorum and one for my VMs. But I still see available capacity 0% so I bet this is the issue. What am I doing wrong in adding the volume?
All replies (22)
Wednesday, December 21, 2011 9:26 AM
Hi,
Please check the following guides to see whether there are any mis-configuration.
Deploying Cluster Shared Volumes (CSV) in Windows Server 2008 R2 Failover Clustering
http://blogs.msdn.com/clustering/archive/2009/02/19/9433146.aspx
Hyper-V: Using Live Migration with Cluster Shared Volumes in Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/dd446679(WS.10).aspx
Best Regards,
Vincent Hu
Wednesday, December 21, 2011 1:15 PM
Hi,
You check storage for SCSI3 PR accepted, is your disk basic. And you can clear stale PR with this command cluster node servernode1 /clear:2 (2 mean 2. disk on the disk management) and try again.
Best Regards,
Hakan YÜKSEL
“Please click "Vote As Helpful" if it is helpful for you and Proposed As Answer”
Blog | LinkedIn
Wednesday, December 21, 2011 6:19 PM
Hi,
Please check the following guides to see whether there are any mis-configuration.
Deploying Cluster Shared Volumes (CSV) in Windows Server 2008 R2 Failover Clustering
http://blogs.msdn.com/clustering/archive/2009/02/19/9433146.aspx
Hyper-V: Using Live Migration with Cluster Shared Volumes in Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/dd446679(WS.10).aspx
Best Regards,
Vincent Hu
Vincent,
I actually used the first link you gave me to setup my cluster. But here is the problem, when I first create the cluster and I select storage, I'm seeing 0% available capacity. The total capacity shows 100GB which is one SAN partition, but what about the other SAN partition that I have connected to the server? Shouldn't the FCM see this automatically?
Wednesday, December 21, 2011 9:52 PM
I'm thinking the problem is how I have my volumes setup, so here is my setup:
Disk2, Basic, 100GB, Reserved
Disk2 is currently the one that is viewable under Storage for total capacity.
Disk3, Basic, 150GB, Online listed as a New Volume NTFS Primary Partition
What is shown in bold is what's the difference that I can see in Disk Management between the two volumes. Am I creating the volume incorrectly? Or do they look different because the other volume is already associated with the cluter?
Friday, December 23, 2011 2:07 PM
Are all the disks available to all nodes that will be involved in the cluster?
Friday, December 23, 2011 4:18 PM
Being that both HyperV host servers can see them, proper access has been given off the SAN. Where exactly are you referring to, so that I can verify the disks are available? Is this off the server? A for the SAN, I'm sure it is available.
Friday, December 23, 2011 4:53 PM
Hi Sorry re-readig the original post i can see the disks are already available under storage in failover cluster manager.
Have you already added these disks to Cluster Shared Volumes?
Friday, December 23, 2011 4:57 PM
Not a problem R.A.F25. So when I select Cluster Shared Volumes, right click and 'add storage' I get an error stating "There are no available disks in the cluster". Up above that screen I see Storage: No disks and Total Capacity 0%. It's not seeing the disks for whatever reason, and more than likely I haven't done something correctly. In Disk Management I see all the disks.
Friday, December 23, 2011 5:32 PM
Ok, so under Storage i assume Disk 2 100GB has been used as Disk Witness? Have you added Disk 3 to the Storage in Failover Cluster Manager? Before you can add disks as CSV's they first need to be added into the FCM storage. Right Click Storage Add a Disk.
Friday, December 23, 2011 6:05 PM
That is correct, the 100GB will be used as the disk witness. When I select Storage under FCM, right click and 'Add a disk' I get the following error:
No disks suitable for cluster disks were found. For diagnostic information about disks available to the cluster, use the Validate a Configuration Wizard to run Storage tests.
I've done this but it only tells me that no disks are available, no other information to help troubleshoot.
I see the disks in Disk Management, but the one used by the cluster is reserved and the other is not. I've tried creating the other volume with a drive letter and without, same result. So I'm thinking I have to configure it a certain way, not sure. I didn't do anything special for the other volume really, so at a loss on that one.
Friday, December 23, 2011 6:43 PM
Ok and again you said the disk is visible in Disk manager on all nodes in the cluster and you are able to bring the disk online in Disk Manger on both nodes
Have you tried creating another volume on the SAN and seeing if you get the same issue?
Cheers Richard
Friday, December 23, 2011 6:56 PM
I think a screenshot would be best here :) Please check image attached, what do you think?
Disk 1, 2, 3 are all SAN volumes. Currently trying to get Disk 2 and 3 in FCM.
Friday, December 23, 2011 7:12 PM
I cant see anthing wrong in the screenshot, the only time i have the same issue is if not all nodes in the cluster have access to the disks.
Cheers Richard
Friday, December 23, 2011 7:21 PM
And that access would be given on the SAN for those volumes, right?
Friday, December 23, 2011 7:25 PM
All nodes in the cluster need to have the disks visable in disk manager. Cheers Richard
Friday, December 23, 2011 7:29 PM
What a downer, because everything seems to be correct. I'll keep digging and hopefully somebody else has an idea. Thanks for the help Richard and taking the time to answer my questions. I appreciate it!
Friday, December 23, 2011 7:32 PM
No problem, hope you get it sorted ill keep thinking and hopefully someone else will have some ideas.Cheers Richard
Monday, December 26, 2011 8:23 AM
Hi,
There isn’t too much useful information from the Disk Management console screen shots.
If you want to create a cluster, you have to create some LUNs form your SAN or other similar devices.
For example, you create two LUNs for a two nodes cluster, one is 500MB for quorum, another 100GB for data.
On node 1, you can see two disks available in Disk Management after you configure iSCSI initiator(or fiber channel) properly. Then you can online two disks, initialize them and create partition on them. On node 2, you have to configure iSCSI initiator too, but don’t need to configure the disks in Disk Management.
Now you can validate the cluster and create it. If the cluster finish properly, it will use the 500MB’s disk as quorum. Or else, you can switch the quorum disk in Failover Cluster console if it use the 100GB’s disk as quorum. In Storage item under Failover Cluster console, you will be able to see both the disks.
Now if you want to add a third 500GB’s disk to the cluster, you can create it on you SAN. As you have configured the iSCSI(or fiber channel) properly, you will be able to find the 500GB’s disk in Disk Management on both nodes. You can online the new disk, initialize it and create partition on it one either of the nodes.
Now in Storage item under Failover Cluster console, you can right click to add the 500GB’s disk to the cluster.
Best Regards,
Vincent Hu
Friday, January 6, 2012 5:27 PM
Hi,
There isn’t too much useful information from the Disk Management console screen shots.
If you want to create a cluster, you have to create some LUNs form your SAN or other similar devices.
For example, you create two LUNs for a two nodes cluster, one is 500MB for quorum, another 100GB for data.
On node 1, you can see two disks available in Disk Management after you configure iSCSI initiator(or fiber channel) properly. Then you can online two disks, initialize them and create partition on them. On node 2, you have to configure iSCSI initiator too, but don’t need to configure the disks in Disk Management.
Now you can validate the cluster and create it. If the cluster finish properly, it will use the 500MB’s disk as quorum. Or else, you can switch the quorum disk in Failover Cluster console if it use the 100GB’s disk as quorum. In Storage item under Failover Cluster console, you will be able to see both the disks.
Now if you want to add a third 500GB’s disk to the cluster, you can create it on you SAN. As you have configured the iSCSI(or fiber channel) properly, you will be able to find the 500GB’s disk in Disk Management on both nodes. You can online the new disk, initialize it and create partition on it one either of the nodes.
Now in Storage item under Failover Cluster console, you can right click to add the 500GB’s disk to the cluster.
Best Regards,
Vincent Hu
Vincent,
I hate to unpropose your response as an answer, but I've already done this procedure. Disk 1, 2, and 3 are all separate volumes on the SAN attached via the iSCSI initiator. But I'm not able to get the disks to be used within the cluster.
Sunday, January 15, 2012 10:22 PM
Did you enable multi path within the iscsi initiator when connecting to the volumes?
Cheers Richard
Friday, December 14, 2012 3:40 PM
Did you ever determine the problem? I'm having the exact same issue. My Quorum disk on the storage is connected, but my other 2TB Lun isn't an available disk
Friday, July 5, 2013 3:43 PM
Hello guys! I´m having the problem FCM does not see any disks, but my configuration is a little bit unique, since this is a lab - I´m running single Hyper-V host, and there is 2 nodes set with W2012. Physical disks are Sata3, this is not a real server with SAN or other real storage solution. First problem is, that I can´t share vhdx disks between 2 nodes. I first attach it to 1st node as iscsi, power it up and fine. At the same time, I cannot attach it to other node (this how it worked on VMware, I´ve done cluster with it), because it´s is in use. Also, I don´t see the disks in FCM, even if it is initializated and formated on Node1.
So main question is, how I should create these disks for cluster usage?