Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

2 Node vSAN cluster shows VMs with reduced availability (66753)

Last Updated: 4/5/2024Categories: TroubleshootingTotal Views: 7676Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

All of the vms on the host have the warning "reduced availability with no rebuild"

"Repair objects immediately" option on the vsan health does not rectify this issue

Clomd.log logs the following message upon trying to repair:

"The version mismatch is from the witness which is on version v3 the data nodes are on version v5
YYYY-MM-DDT06:01:02.595Z 327036 (1072927856928)(opID:1804363429)CLOM_LogOpReport: OpReport: type:10 status:Not found reason:13
YYYY-MM-DDT06:01:02.595Z 327036 Total nodes:3 Total disks:17 disksUsed:0 phyDisksUsed:0 disksNeeded:1 disks decommisionning:0 disks with Node decommisionning:0 unhealthy disks:0 disks with unhealthy ssds or nodes:0 disks with insufficient space:0 disks with max components:0 disks with storage type mismatch:0 disks with version mismatch:1 disks in witness nodes:0 disk failed affinity/anti-affinity rule:0"

Purpose

The purpose of this KB article is to advise the best course of action when the objects have reduced availability due to discrepancies in the disk format version.

Cause

The cause of this issue is due to the fact that the witness appliance is not on the same disk format version as the two data nodes. In this instance/example in the symptoms, the data nodes are on disk format version 5 while the witness is on disk format version 3. This leads to a situation where the version 5 objects can not rebuild with a version 3 object.

Impact / Risks

In the case of a failure the version 3 objects could not be used to rebuild the objects. This can also cause the witness node to be isolated from the cluster.

Resolution

In order to resolve this issue please upgrade the witness appliance to a version where it can have a consistent/same disk format version with the data nodes.

More information about on-disk format versions can be found in the following KB.
Understanding vSAN on-disk format versions and compatibility

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
VMware Integrated OpenStack の診断情報の収集 (2125261)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 8.0.x

VMware vSAN 7.0.x

VMware vSAN 6.x

Take Our Survey

Support Assistant