Akulsh
asked on
Windows Cluster issue - Quorum Disk online but absent
In one of our SQL cluster (both nodes vSphere VMs), after a reboot, the quorum disk is no longer seen in Parent Windows Cluster and SQL cluster fails. The quorum disk is online but it does have an error:
Have run "Configure Cluster Quorum Settings" wizard many times but it make no difference. Added a fresh disk to act as Quorum but that is also behaving exactly like the old Quorum disk. SQL server is running fine. But cluster is in Failed state and services will not start when failover occurs.
(See enclosed screen-shot which also shows how it is in the healthy SQL cluster.) Both Window OS and SQL are 2016. How may I make Quorum Disk healthy? Thanks.
Event ID: 1795 Source: Microsoft-Windows-Failover Clustering
Cluster physical disk resource terminate encountered an error.
Physical Disk resource name: SAN2-Quorum
Device Number: 6
Device Guid: {85bf95e3-f896-c760-154b-c baecdd743f d}
Error Code: 2
Additional reason: OpenPartitionFailure
Cluster physical disk resource terminate encountered an error.
Physical Disk resource name: SAN2-Quorum
Device Number: 6
Device Guid: {85bf95e3-f896-c760-154b-c
Error Code: 2
Additional reason: OpenPartitionFailure
Have run "Configure Cluster Quorum Settings" wizard many times but it make no difference. Added a fresh disk to act as Quorum but that is also behaving exactly like the old Quorum disk. SQL server is running fine. But cluster is in Failed state and services will not start when failover occurs.
(See enclosed screen-shot which also shows how it is in the healthy SQL cluster.) Both Window OS and SQL are 2016. How may I make Quorum Disk healthy? Thanks.
Can you add Storage to the cluster to bring it back in? If you right click on the Cluster and choose to reconfigure the Quorum and choose a disk, will it pull it back in the cluster group?
ASKER
I have reconfigured Quorum disk many a times, but it still does not show up in Windows cluster. It is already part of the cluster group, but not a healthy Quorum disk.
As mentioned earlier, the disk error is "OpenPartitionFailure".
Adding a brand new disk to cluster as a fresh Quorum Disk did not help. Thanks.
As mentioned earlier, the disk error is "OpenPartitionFailure".
Adding a brand new disk to cluster as a fresh Quorum Disk did not help. Thanks.
If you run Get-Disk in powershell on the node with the quorum disk on it, do you see the disk and what is the type of disk?
ASKER
This is the output of Get-Disk
Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition
Style
------ ------------- ------------- ------------ ----------------- ---------- ----------
0 VMware Vir... 6000c29a8c133ed261d7107d89 f4fc8c Healthy Online 300 GB MBR
5 COMPELNT C... 000583c2-00000013 Healthy Online 200 GB MBR
6 COMPELNT C... 000583c2-00000014 Healthy Online 2 TB MBR
2 COMPELNT C... 000583c2-00000010 Healthy Online 1 GB MBR
3 COMPELNT C... 000583c2-00000011 Healthy Online 1.2 TB MBR
4 COMPELNT C... 000583c2-00000012 Healthy Online 600 GB MBR
The 1 GB disk is the Quorum disk.
Number Friendly Name Serial Number HealthStatus OperationalStatus Total Size Partition
Style
------ ------------- ------------- ------------ ----------------- ---------- ----------
0 VMware Vir... 6000c29a8c133ed261d7107d89
5 COMPELNT C... 000583c2-00000013 Healthy Online 200 GB MBR
6 COMPELNT C... 000583c2-00000014 Healthy Online 2 TB MBR
2 COMPELNT C... 000583c2-00000010 Healthy Online 1 GB MBR
3 COMPELNT C... 000583c2-00000011 Healthy Online 1.2 TB MBR
4 COMPELNT C... 000583c2-00000012 Healthy Online 600 GB MBR
The 1 GB disk is the Quorum disk.
Sounds like there is something wrong for the partition on the disk. Hard to tell. If you run Get-Partition for DiskNumber 1? What is there?
ASKER
Disk #1 is the second fresh Quorum disk I added yesterday. I have taken it offline since it did not help. Here is the output of Get-disk command which I had omitted previously:
1 COMPELNT C... 000583c2-0000001b Healthy Offline 1 GB MBR
1 COMPELNT C... 000583c2-0000001b Healthy Offline 1 GB MBR
ASKER
Get-partition shows this for the Quorum disk (J:):
DiskPath: \\?\Disk{85bf95e3-f896-c76 0-154b-cba ecdd743fd}
PartitionNumber DriveLetter Offset Size Type
--------------- ----------- ------ ---- ----
1 J 65536 1021 MB IFS
DiskPath: \\?\Disk{85bf95e3-f896-c76
PartitionNumber DriveLetter Offset Size Type
--------------- ----------- ------ ---- ----
1 J 65536 1021 MB IFS
There is really only one reason I can think of that the quorum disk is not found, is that the drive is not available on all nodes of the cluster. Did you run a cluster test for storage?
ASKER
Have run Cluster Validation many times. The storage section shows no error. When I shutdown one node, all disks, including Quorum Disk, show up on the other node.
Validation report has this Warning; "The Core Cluster Resource Group does not contain a file share witness or a disk witness. This is a required resource for the group."
Thanks.
Validation report has this Warning; "The Core Cluster Resource Group does not contain a file share witness or a disk witness. This is a required resource for the group."
Thanks.
That is what it seems is that the drive that you want to use for the Quorum, seems to not be able to be seen by both nodes or it would show up in the Add Storage from the Disks.
ASKER
It is already added in Storage. I also added a brand new disk for Quorum, but it did not improve things.
I am thinking of giving this command:
I am thinking of giving this command:
Clear-ClusterDiskReservati on -Disk #
Could it help? Thanks.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.