Hello,
sk84
"1.) Yes, installing ESXi on these disks is supported, so you could ignore this warning. See: VMware Knowledge Base"
Not necessarily the case - for instance it is not supported to have ANY VMFS on H730 controllers used for vSAN, even just for logging/dumps and even the small VMFS created by default on install on boot device if not unselected/removed after:
VMware Knowledge Base
(and yes I am aware that kb says 'with lsi_mr3 driver' but I still wouldn't mix VMFS with vSAN on these controllers regardless)
I see Avago and MegaRAID there so in addition to them having never applied HCL JSON update there is a good chance these are H730 controllers (with ancient drivers+firmware).
ManivelR
There appear to be at least two VMFS partitions in your screenshot (expanding the tabs and/or zooming out your browser helps here), you are using multiple controller (vmhba0 + vmhba2) on each host or different vmhba numbers on different hosts? If this is the case you will notice both are stating they have VMFS devices on them so likely not just default VMFS from boot device, that plus one of them looks to have a default-ish name and the other a given-name (VCS-...). Then again the test only indicates '5 items' and you said it is a 4-node cluster so this would indicate this is inconsistently misconfigured :smileygrin: .
While not mandatory to install storcli, this would be advised for visibility and improvements in interactability with the controller.
And as sk84, if you are ever in doubt about what a health check does or means, this is why we include handy URL links to kb articles providing additional details about every check (which can of course be copied if you don't have direct internet access from there).
Bob