Mounting vVOL datastore on new ESXi hosts fails with "General System Error"
search cancel

Mounting vVOL datastore on new ESXi hosts fails with "General System Error"

book

Article ID: 384212

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

  • While attempting to mount vVOL Datastore, you may receive a "General System Error".
  • There are existing hosts accessing the same vVOL Datastore without issues.
  • The vVOL Protocol Endpoint is not available on the new host.
  • The VASA provider is missing from host configuration, despite it being configured on vCenter and having online status.
  • vvold.log shows that vvold service will not start:


2020-10-09T00:46:03.669Z error vvold[2154094] [Originator@6876 sub=Default] VVold SI:main, no VVol config available, exiting
2020-10-09T00:46:03.680Z [/etc/init.d/vvold[2154105]: /etc/init.d/vvold stopnomemclear, PID 2154105]
2020-10-09T00:46:03.782Z [/etc/init.d/vvold[2154105]: vvold stopped.]
2020-10-09T00:46:03.893Z [/etc/init.d/vvold[2154105]: PID 2154105 removed /var/run/vmware/vvold-done-calling-start]
2020-10-09T00:46:04.627Z [/etc/init.d/vvold[2154047]: WaitVvoldToComeUp /var/run/vmware/.vmware-vvol.started created]
2020-10-09T00:46:04.642Z [/etc/init.d/vvold[2154047]: vvold stopped after start!]
2020-10-09T00:46:04.646Z [/etc/init.d/vvold[2154047]: /var/run/vmware/.vmware-vvol.started is not created]
2020-10-09T00:46:04.764Z [/etc/init.d/vvold[2154047]: Successfully cleared vvold memory reservation]
2020-10-09T00:46:04.768Z [/etc/init.d/vvold[2154047]: PID 2154047 Created /var/run/vmware/vvold-done-calling-start]
2020-10-09T00:46:04.773Z [/etc/init.d/vvold[2154047]: Removed /var/run/vmware/.vmware-vvol.lock-dir]

Environment

  • VMware vSphere ESXi 6.x
  • VMware vSphere ESXi 7.x
  • VMware vSphere ESXi 8.x

Cause

  • vVOLS are not configured for the host from SAN end.
    • The host will not receive the VASA provider information nor be able to mount the vVOL datastore until the Protocol Endpoint LUN is mapped to and accessible by the host.

Resolution

  • Ensure that the Protocol Endpoint and vVOL Datastore is properly mapped to the hosts from in the SAN configuration. If needed, please contact the SAN vendor for assistance. 
  • To verify if the protocol endpoint is available to host, use esxcli command from ssh session to host:

esxcli storage vvol vasaprovider list

  • To verify if the protocol endpoint is available to host, use esxcli command from ssh session to host:

esxcli storage vvol protocolendpoint list

  • If using self-signed certificates, verify that Host Certificate settings are correct: 

https://knowledge.broadcom.com/external/article/318746/esxi-67-u3-or-later-host-newly-added-to.html

Additional Information

Powered by Wolken Software