To resolve this issue, follow below-provided steps, please do not skip
lrwxrwxrwx 1 root root 49 Nov 26 12:06 store -> /vmfs/volumes/534c2849-########-####-##########4c
2. Identify the disk device by using the below command:
vmkfstools -P /vmfs/volumes/vmfs/volumes/534c2849-########-####-##########4c
Example:
[root@hostname:~] vmkfstools -P /vmfs/volumes/572398ac-########-####-#########a0
vfat-0.04 file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 299712512 (36586 file blocks * 8192), 299089920 (36510 blocks) avail, max supported file size 0
UUID: 572398ac-########-####-##########a0
Partitions spanned (on "disks"):
mpx.vmhba32:C0:T0:L0:8
Is Native Snapshot Capable: NO
3. Re-format the device disk from above step with vfat filesystem (this will create a new UUID) vmkfstools -C vfat /dev/disks/mpx.vmhba32:C0:T0:L0:8
[root@hostname:~] vmkfstools -C vfat /dev/disks/mpx.vmhba32:C0:T0:L0:8
create fs deviceName:'/dev/disks/mpx.vmhba32:C0:T0:L0:8', fsShortName:'vfat', fsName:'(null)'
deviceFullPath:/dev/disks/mpx.vmhba32:C0:T0:L0:8 deviceFile:mpx.vmhba32:C0:T0:L0:8
Checking if remote hosts are using this device as a valid file system. This may take a few seconds...
Creating vfat file system on "mpx.vmhba32:C0:T0:L0:8" with blockSize 1048576 and volume label "none".
The filesystem was created but mount failed on device "mpx.vmhba32:C0:T0:L0:8".: Not found.
Successfully created new volume: 5bec6252-########-####-##########a0
[root@hostname:~] vmkfstools -P /vmfs/volumes/572398ac-########-####-#########a0
vfat-0.04 file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 299712512 (36586 file blocks * 8192), 299089920 (36510 blocks) avail, max supported file size 0
UUID: 572398ac-########-####-##########a0
Partitions spanned (on "disks"):
naa.644a8420135982001e83017d0ce370f6:8
Is Native Snapshot Capable: NO
4. Re-create symlink with new UUID:[root@hostname:~] ln -snf /vmfs/volumes/<new-UUID from above step> store
5. Copy packages, var under locker directory from working host to non-working host. (Same version, build can be different)
6. Retry the scan/remediation.