Following reboot of ESXi 8.0 U2 hosts with configured NFSv3 datastores, these datastores will not be automatically mounted as expected.
ESXi 8.0 U2 using NFSv3 datastores.
This issue occurs due to an issue in ESXi NFS Client firewall rule configurations which are not persisted across reboots - this issue is resolved in ESXi 8.0 U3 (Date: 2024/06/25, build: 24022510).
To prevent this issue from occurring, upgrade to ESXi 8.0 U3 (Date: 2024/06/25, build: 24022510) which includes the fix for this issue.
Workaround:
The unmounted datastore(s) can be listed using the following command where ##.##.#.# is the IP of the NFS server(s):
[root@localhost:~]esxcli storage nfs list
Volume Name Host Share Vmknic Accessible Mounted Connections Read-Only isPE Hardware Acceleration
----------- ---------- ---------------------- ------ ---------- ------- ----------- --------- ----- ---------------------
NFS-DS-NAME ##.##.#.# /NFS-MOUNT-NAME None false false 1 false false Unknown
The firewall entries for the NFS datastore server(s) can be manually added using the following command run on the host via SSH, where ##.##.#.# is the IP of the NFS server(s):
[root@localhost:~] localcli --plugin-dir /usr/lib/vmware/esxcli/int/ networkinternal firewall firewallRuleset allowedip add -r nfsClient --service-name nfsClient -i ##.##.#.#
Following this action the NFS datastore(s) should be mountable.