Informational

First, you need to know the path to the partition (naa.xxxxxx:1). Run the following command to display a list with Volume Name, VMFS UUID and Device Name:

esxcli storage vmfs extent list

[root@ESXi-04:~] esxcli storage vmfs extent list
Volume Name            VMFS UUID                            Extent Number  Device Name                                                               Partition
---------------------  -----------------------------------  -------------  ------------------------------------------------------------------------  ---------
Datastore ESXi-04 SSD  640fa3f8-8f12db0e-c7cc-6c4b9057f451              0  t10.ATA_____SanDisk_SD7SB6S128G1001_________________161413403671________          1
Datastore ESXi-04 M2   640fa544-d901bf18-33b5-6c4b9057f451              0  t10.NVMe____SAMSUNG_MZVLW128HEGR2D000L1______________2580B381B4382500             3

If we want to scan VMLUN_01 we have to combine the Device Name (naa.60a98000646e6c…) and the partition number (1) with a “:”.

[root@ESXi-04:~] voma -m vmfs -f check -d /vmfs/devices/disks/t10.NVMe____SAMSUNG_MZVLW128HEGR2D000L1______________2580B381B4382500:3
Checking if device is actively used by other hosts
Scanning for VMFS-6 host activity (4096 bytes/HB, 1024 HBs).
Running VMFS Checker version 2.1 in check mode
Initializing LVM metadata, Basic Checks will be done
Phase 1: Checking VMFS header and resource files
   Detected VMFS-6 file system (labeled:'Datastore ESXi-04 M2') with UUID:640fa544-d901bf18-33b5-6c4b9057f451, Version 6:82
Phase 2: Checking VMFS heartbeat region
Phase 3: Checking all file descriptors.
Phase 4: Checking pathname and connectivity.
Phase 5: Checking resource reference counts.

Total Errors Found:           0