Hi Bob,
Tried both:
(Screenshot) ls -lah /vmfs/volumes/cluster1_vsanDatastore/
The two VMs in my original image do show symlink > UUID, but strangely, each ALSO have another entry where the same UUID does not have a symlink, as highlighted in the screenshot.
Not sure if normal.
Also tried reloading with vim-cmd vmsvc/reload <correct respective VMID>, no change.
RVC output:
| Header 1 |
|---|
/vc1/dc1/computers/cluster1> vsan.check_state -r ./ 2019-03-10 08:30:17 -0800: Step 1: Check for inaccessible vSAN objects 2019-03-10 08:30:22 -0800: Step 1b: Check for inaccessible vSAN objects, again 2019-03-10 08:30:22 -0800: Step 2: Check for invalid/inaccessible VMs 2019-03-10 08:30:22 -0800: Step 2b: Check for invalid/inaccessible VMs again 2019-03-10 08:30:22 -0800: Step 3: Check for VMs for which VC/hostd/vmx are out of sync Did not find VMs for which VC/hostd/vmx are out of sync /vc1/dc1/computers/cluster1> |
... looks fine I guess?
Still don't know what's going on. VMs are still healthy. Can vMotion, Storage vMotion, remove from inventory then re-register. No problem, they still boot and run fine.
The only problem still is that they are only showing UUIDs instead of names in Cluster > Monitor > Virtual Objects.