There are several reasons that you may not be able to browse an inaccessible datastore, however if the datastore is still browsable from the Host UI or the Host SSH session then we can confirm that this is an issue with vCenter connectivity to the host. To see if this is the issue you are facing you will need to:
To test if you can browse the files from the host:
https://[IP of ESXi Host]/uiIf you can see and browse the files here but not in the vCenter client then this could be being caused by the vCenter attempting to log in to the host with the wrong ESXi credentials. To confirm that this is the case, open an SSH session to the vCenter:
YYYY-MM-DDTHH:MM:SS.Z warning vpxd[#####] [Originator@#### sub=InvtHostCnx opID=HostSync-host-######-######] Exception occurred during host sync; Got method fault; [vim.HostSystem:host-######, 10.##.##.##], e: N3Vim5Fault12InvalidLogin9ExceptionE(Fault cause: vim.fault.InvalidLogin-->
VMware vCenter Server 9.x
VMware vCenter Server 8.x
VMware vCenter Server 7.x
Whenever you restart the management agents, reboot the vCenter, or restart the vpxd agent, vCenter randomly chooses a host to start services on. When the host is chosen, vCenter will log in to the host with the latest credentials. However, if the password has been changed or lost (this can happen due to snapshots, backups, or rollbacks) then we cannot start the management agents on the host.
This leads to several issues but since vCenter uses the management agents to communicate with the host, this will lead to us being unable to browse the datastore from the vCenter. It can also impact backups and prevent HA from functioning properly since it will prevent services from starting.
To resolve this:
If you cannot browse the files from the Host UI then see: Datastore shows inaccessible state in vCenter and investigate the backend disconnection to the LUN