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

Disks claimed for a vSAN Datastore are not visible in the Disk Management tab in vCenter but can be observed via the ESXi host command line. (67386)

Last Updated: 5/29/2023Categories: Best PracticesTotal Views: 11809Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Disks claimed for a vSAN Datastore are not visible in the vCenter Web Client <vSAN Cluster> Configure>vSAN>Disk Management.

Disks can be observed via the command line by running any of the commands below:
esxcli vsan storage list |grep -i cmmds
In CMMDS: true
In CMMDS: true

vdq -iH
Mappings:
DiskMapping[0]:
SSD:  mpx.vmhba2:C0:T0:L0
MD:  mpx.vmhba2:C0:T1:L0

vdq -iq
[
{
"Name"     : "mpx.vmhba2:C0:T1:L0",
"VSANUUID" : "529af87f-a010-db5f-aaec-9c90df2cadf8",
"State"    : "In-use for VSAN",
"Reason"   : "None",
"IsSSD"    : "1",
"IsCapacityFlash": "1",
"IsPDL"    : "0",
"Size(MB)" : "16384",
"FormatType" : "512n",
},

{
"Name"     : "mpx.vmhba2:C0:T0:L0",
"VSANUUID" : "52b5af7a-644a-c68f-e81e-4c0c79246d26",
"State"    : "In-use for VSAN",
"Reason"   : "None",
"IsSSD"    : "1",
"IsCapacityFlash": "0",
"IsPDL"    : "0",
"Size(MB)" : "8192",
"FormatType" : "512n",
},

{
"Name"     : "mpx.vmhba0:C0:T0:L0",
"VSANUUID" : "",
"State"    : "Ineligible for use by VSAN",
"Reason"   : "Has partitions",
"IsSSD"    : "0",
"IsCapacityFlash": "0",
"IsPDL"    : "0",
"Size(MB)" : "8192",
"FormatType" : "512n",
},

]

Purpose

Isolate any vSAN layer issues and confirm if this is a cosmetic display issue whereby the vCenter Web Client interface is unable to recognize the disks used in the vSAN layer.

Cause

vCenter is on an older build than that of the hosts. This leads to vCenter not being able to recognize the disks even though they are mounted and eligible for use by vSAN. You can confirm this by checking the build version number in the summary tab of the vCenter icon and in each ESXi in the vSAN cluster.

For more information regarding vCenter/ESXi version mismatch see KB:

vCenter version to ESXi version (68174)

You can also manually check the versions in the links below and validate the release date. The vCenter version should have the same release date as the ESXi or sooner.

vCenter build versions: https://kb.vmware.com/s/article/2143838

ESXi build versions: https://kb.vmware.com/s/article/2143832

Impact / Risks

There is no impact reported, this is a mere display issue that does not affect vSAN operations.

Should there be a need to add/remove a disk/diskgroup before the vCenter can be upgraded, then this can be done via the command line as per the instructions in the following KB article:

How to manually remove and recreate a vSAN disk group using esxcli (2150567)

Resolution

Upgrade vCenter to an equivalent or higher build than what the hosts are on. This will allow vCenter to recognize the vSAN disks and create/delete diskgroups with them. At the end of the upgrade, the vCenter Server will need to be rebooted which will not have any impact on the vSAN layer however the only impact is that the vCenter Web Client interface will be unavailable until the vCenter Server comes back online.

Workaround

There is no current workaround since the issue is a vCenter Web Client display issue due to not following the recommended order/sequence when upgrading VMware products, where vCenter must be upgraded before the ESXi hosts.

Upgrading VMware products sequence: https://kb.vmware.com/s/article/53710

Related Information

Upgrading VMware products sequence: https://kb.vmware.com/s/article/53710

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
•
在 vCenter 6.7 Update 2 中，vSphere Client （HTML5）/vSphere Web-Client （Flash）加载虚拟机摘要页面速度较慢 (68154)

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

VMware vSAN 6.6.x

VMware vSAN 6.5.x

VMware vSAN 6.0.x

Take Our Survey

Support Assistant