You *need* to have a service contract - at least when using critical vm´s on it.
Now - IF i had this in a testlab (and ONLY in a testlab). And all in the testlab would be totally for fun and play. Only THEN I would EVENTUALLY shutdown all the running VMs residing on the VSAN and after that I would shutdown all hosts participating in the VSAN cluster. After that i´d boot em up again and check if the error persists. It it would persist i would EVENTUALLY think about disabling VSAN and re-enabling it again.
But this is only trial and error. This is NO advice to you. It is all hypothetical. So don´t do this!
I´d *really* suggest to implement a fresh contract / renew yours and then open an official case with vmware.