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

Upgrading vSAN On-disk format version fails and remains at v3 (57745)

Last Updated: 6/15/2023Categories: How toTotal Views: 11643Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vSAN object versions still at v3 after On-disk Format v5 upgrade

These issues are seen when the vCenter Server version is at 6.7 while hosts are at ESXi 6.5 during the vSAN On-disk Format version upgrade

After disk version upgrade, the following warning appears beside Disk format version under vSAN cluster > Configure > General:
"Disk Format Version: All xx disk on version 5.0 but with old vSAN objects"

Errors found in the vCenter /var/log/vmware/vpxd/vpxd.log logfile:

Error Type: VsanFault
Description Id: com.vmware.vsan.diskconvertion.tasks.conversion

INFO vsan-mgmt[DFC-domain-c12_f5583b58-8b35-11e8] [VsanVcDiskFormatConverterImpl::_UpdateProgress opID=f5583b58-8b35-11e8] Progress: 10
INFO vsan-mgmt[DFC-domain-c12_f5583b58-8b35-11e8] [VsanVcDiskFormatConverterImpl::ConvertDisks opID=f5583b58-8b35-11e8] All online disk updates complete
WARNING vsan-mgmt[DFC-domain-c12_f5583b58-8b35-11e8] [VsanVcDiskFormatConverterImpl::ConvertDisks opID=f5583b58-8b35-11e8] Exception in online upgrade: (vim.fault.VsanFault) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
msg = '',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) [
(vmodl.LocalizableMessage) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
key = 'com.vmware.vsan.diskconversion.msg.bumpupversionerror',
arg = (vmodl.KeyAnyValue) [],
message = 'Failed to bump up format version for diskmapping naa.xxxx, Failed to get VsanInfo operation lock for diskOpLockan operation is currently in progress(locked pid: 0), error: /tmp/.vsanDiskOpLock.lock.LOCK: timout waiting for lock after 30 seconds. Lock is currently held by process 838647 (python: python /usr/lib/vmware/vsan/perfsvc/vsanperfsvc.pyc)'
}

Cause

In vSAN 6.7, the vCenter vpxd service upgrades the vSAN on disk format version per disk per group

When vSAN On-disk Format version on disk groups is being upgraded, the disk operation lock must be acquired to continue the upgrade operation, if this lock cannot be acquired within 30 seconds, the upgrade request will fail.

If a vSAN host has more than 1 disk group to be upgraded, there can be conflict on acquiring this lock, and if a disk operation lock takes more than 30s, other disk group requests on this host will fail causing the on disk upgrade operation to fail

Impact / Risks

Full features of v5 will not be available as the object will be on v3, but there is no potential risk to data

Resolution

Upgrade all ESXi hosts to 6.7, it is advisable to have ESXi and vCenter Server on same release version before running an On-disk Format version upgrade

Related Information

Following workaround is available  :

Login to vCenter Server & make a backup copy of this file:

cp /usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVcDiskFormatConverterImpl.py /usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVcDiskFormatConverterImpl.py.backup

Open file /usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVcDiskFormatConverterImpl.py, go to LINE2725

Change lines

if (ssd.vsanDiskInfo and

(ssd.vsanDiskInfo.formatVersion in ONLINE_UPGRADE_DISKGROUP_VERION)):

WITH

if (ssd.vsanDiskInfo and
(ssd.vsanDiskInfo.formatVersion in ONLINE_UPGRADE_DISKGROUP_VERION) and
(ssd.vsanDiskInfo.formatVersion != targetVersion)):

Restart vSAN health service via UI or through command on vCenter Server
service-control --stop vmware-vsan-health
service-control --start vmware-vsan-health

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
•
vSAN -- 健全性サービス -- プロアクティブ テスト -- ネットワーク パフォーマンス テスト (58895)

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 6.6.x

VMware vSAN 6.5.x

Take Our Survey

Support Assistant