Loading

×Sorry to interrupt
CSS Error

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

Cannot see some or all storage devices in VMware vCenter Server (1016222)

Last Updated: 3/22/2021Categories: TroubleshootingTotal Views: 253252Language:
Chinese (Simplified)JapaneseEnglish

9 like this article

Subscribe to get an email
newsletter with new updates

9 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

You cannot see some or all storage devices or the list is incomplete and missing the intended device(s) when you try to perform these operations:

Creating or formatting a new VMFS datastore using the Add Storage feature.

Extending an existing VMFS datastore by using another distinct LUN as an extent.

Extending an existing VMFS datastore by utilizing unallocated space made available within the same LUN (via a previous enlargement process via the SAN array).

Creating Raw Device Mappings (RDMs) for use with Virtual Machines.

In ESXi, the device can be seen by the ESXi host, but the datastore is inactive under storage.

You may an error similar to this in the vmkernel.log:

cpu0:946544)ScsiDevice: 4592: naa.60a9800037542d684924426364375152 device :Open count > 0, cannot be brought online

You have already:

Presented one or more LUNs on the SAN array and presented it to your VMware ESXi Servers.

Connected your VMware vSphere Client to the VMware vCenter Server hostname or IP address.

The VMware ESXi servers have rescanned their HBAs from the Configuration tab's Storage Adapters view.

The LUNs are visible under Storage Adapters.

Cause

The general cause of this issue is the non-uniform presentation characteristics of the SAN LUNs across the managed VMware ESXi servers. A requirement is having a uniform or consistent presentation of LUNs across all managed VMware ESXi Servers. Specifically, the LUN ID for each respective LUN must match between all VMware ESXi Servers.

Identifier Specifics:

VMware ESXi above rely on the Understanding SCSI Check Conditions in VMkernel logs during rescan operations device identifier to identify and distinguish between multiple devices. Supported identifiers are:

T11 Network Address Authority (NASA and NAA) 64 and 128-bit integer values, such as:

naa.60060160c5602100ce2236293e7edd11 or vml.020001000060060160c5602100ce2236293e7edd11524149442035

Extended Unique Identifier (EUI) such as:

eui.02004567A425678D

Storage Name Service (SNS) such as:

iqn.2001-05.com.vmware:storage.san.sys.xyz

T10 identifiers.

iSCSI Qualified Name (IQN) identifiers.

If the device does not support VPD page 0x83, then it will be assigned an MPX identifier value, such as
mpx.vmhba0:C0:T0:L0.
This is typically the case for local disks which could not be physically shared, rather than SAN LUNs.

Resolution

Background

VMware vCenter facilitates numerous storage filters to determine using devices for potentially destructive operations such as formatting, creating extents, and creating Raw Device Mappings (RDMs) for use with VMs. There are additional filters in place to account for presentation inconsistencies (or non-uniform presentations) among managed VMware ESXi hosts in the datacenter.

Rules and considerations for these filters are:

VMFS Filter

config.vpxd.filter.vmfsFilter

The LUN is already being used as a datastore on the same host.

The LUN is already being used as a datastore on a different host.

RDM Filter

config.vpxd.filter.rdmFilter

The LUN is already being used as an RDM on the same host.

The LUN is already being used as an RDM on a different host.

Rescan Filter

config.vpxd.filter.hostRescanFilter

VMware ESXi performs automated rescans of VMFS datastores after any datastore configuration operation, including Create, Expand, Extend, Remove, and when upgrading to newer versions of VMFS.

This helps vCenter to offer centralized management by ensuring that ESX hosts provide consistent views of the storage available to them.

Same Host and Transports Filter

The operation of extending a VMFS datastore can utilize entire Logical Unit Numbers (LUNs) and partitions. This filter ultimately prevents corruption and degraded performance. There are several cases where this filter is triggered:

Multiple VMware ESXi hosts managed by VMware vCenter can see a datastore but the extent candidate is visible only on some of the hosts, rather than all.

Your datastore is a local transport type (such as Block or Parallel) and you are attempting to extend it with a datastore of a shareable transport type (such as Fibre Channel or iSCSI), or vice-versa.

There is no uniform presentation between multiple ESXi Servers.

In effect, this filter will remove extent candidate LUNs which are not seen on all of the same hosts as the datastore that is being extended. The non-uniform presentation will result in this filter taking action and declining candidacy for several of the operations, either making the candidate list partial, or empty.

For more information, see Storage Filtering.

If your host LUN IDs are not consistent across the managed VMware ESXi Servers, schedule downtime and configure them for consistent or uniform presentation, ensuring each managed ESXi hosts see each respective LUN with the same LUN ID.
If necessary, work with your storage array vendor to perform this operation.

To verify whether presentation efforts are resulting in inconsistency across the datacenter, see: Identifying disks when working with VMware ESXi/ESX.

For further information on presentation specifics, see the vSphere Storage for vSphere and Fibre Channel SAN Configuration Guide or the iSCSI SAN Configuration Guide for vSphere.

About vSphere Storage

Related Information

一つ以上の RDM のディスクが接続された仮想マシンの移行が、次のエラーで失敗する：Target disc should be different than the source disc, unable to access file
VMware vCenter Server または VirtualCenter で一部または全部のストレージ デバイスが表示されない
在 VMware vCenter Server 或 VirtualCenter 中看不到部分或全部存储设备

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 8.0

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant