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

"Lost access to volume" messages with vSAN (59220)

Last Updated: 8/23/2023Categories: InformationalTotal Views: 15781Language:
Chinese (Simplified)English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

In the /var/log/hostd.log file, you see entries similar to:

2015-07-02T02:00:11.675Z [4F1E1B70 info 'Vimsvc.ha-eventmgr'] Event 205 : Lost access to volume 54f89e21-4427e506-b968-a0369f519998 (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
2015-07-02T02:00:37.055Z [4F480B70 info 'Vimsvc.ha-eventmgr'] Event 210 : Successfully restored access to volume 54f89e21-4427e506-b968-a0369f519998 (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX) following connectivity issues.

2015-07-02T02:00:37.055Z [4F480B70 info 'Vimsvc.ha-eventmgr'] Event 210 : Successfully restored access to volume 54f89e21-4427e506-b968-a0369f519998 (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX) following connectivity issues.

In vCenter Server, you see an event similar to:

Lost access to volume 54f89e21-4427e506-b968-a0369f519998 (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.

In this instance, shown ID  XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX is not referring to a volume/datastore, but to the affected object on the vSAN datastore. These messages are similar to a VMFS volumes when there is too high latency or interruptions when accessing the data.

Purpose

To inform about the meaning of "Lost access to volume" messages on vSAN clusters.

Cause

Any ESXi is writing and processing periodic heartbeats to it's VMFS filesystems. When there are issues updating heartbeats due to underlying vSAN storage instability, these heartbeats will timeout and "Lost access to volume" is logged in the vmkernel.log file.

On vSAN-enabled clusters the folders of virtual machines (called "VM Namespace") are using a special form of VMFS filesystems to incorporate required files for virtual machines, like the .vmx configuration file, .vmdk descriptor files, vmware.log files, etc.

These vSAN cluster instability can, but not limited to, caused by any misbehaving disks in the entire vSAN environment (on any node), network latency or instability of the vSAN network, any sort of congestion, etc.

Resolution

There are multiple possible reasons when such issues are observed. Please validate following:

The "vSAN health check" must be run to verify the state of vSAN and validate whether any issues exist. As an administrator it must be run and checked regularly.

All virtual machines must be compliant with applied storage policy.

Verify a stable, performant network connectivity on the vSAN network.

Verify if any disks on the vSAN environment are nearing it's end of lifespan (e.g. "Write Endurance" for any disks)

Should issues still exist, please open a support case with VMware.

Related Information

Understanding lost access to volume messages in ESXi 6.x/7.x (2136081)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

POLICY_COMPLIANCE_2.PNG

POLICY_COMPLIANCE_CHECK_4.PNG

POLICY_COMPLIANCE_3.PNG

Additional Resources

KB
•
Windows 10 で PCOIP 経由で Horizon View 仮想デスクトップ (VDI) にログインするとブラック スクリーンが表示される (1028332)

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

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vSphere Web Client を使用した Distributed Switch 構成のエクスポート/インポート/リストア (2034602)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

Take Our Survey

Support Assistant