Datastores not visible after a power outage and listing filesystem reports with error: "GetUnmountedVmfsFileSystemsInt: fsUUID is null, skipping naa.####################""

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• iSCSI datastores are not visible to the ESXi host.
• Virtual machines shows invalid.

• Listing the filesystem from ESXi host cli may take lot of time and report with below errors:

[root@Hostname/var/log] localcli storage filesystem list
GetUnmountedVmfsFileSystemsInt: fsUUID is null, skipping naa.#############################02:1

• Above problematic storage device which is not getting queried or not available to hostd are part of the datastore which is configured as multiple extent and this can be validated by running the below command from ESX cli.

[root@Hostname:/] vmkfstools -P -h /vmfs/volumes/Datastore1
VMFS-6.82 (Raw Major Version: 24) file system spanning 2 partitions.
File system label (if any): Datastore1
Mode: public
Capacity 15 TB, 7.0 TB available, file block size 1 MB, max supported file size 64 TB
Disk Block Size: 512/512/0
UUID: ########-########-####-############
Partitions spanned (on "lvm"):
        naa.##############################01:1
        naa.##############################02:1

Environment

VMware vSphere ESXi 7.x

VMware vSphere ESXi 8.x

Cause

In a multiple extent configuration one or more storage devices backing the datastore fails to establish the connectivity to the ESXi host after a power outage which leads the datastore lose the connectivity to ESXi host and report missing.

Resolution

Rescanning of storage devices and adapters from host UI helps in getting the storage device connectivity established on ESXi host. 

Rescanning may work only when the iSCSI connectivity issues are fixed.

All shared iSCSI datastores missing from a single ESXi Host

 

 

Additional Information

Troubleshooting ESXi connectivity to iSCSI arrays using software initiators