Hi CFrank[NAME],  I suspect an issue on the ESX side of things, not the VSA. But not sure. I also suspect that changing the HW version may cause issues on the VSA. One odd thing is that checking my VSAs here, the HW version is 11. And yours is 10. That seems odd to me.  If you open your .vmx file in a text editor, what do you see here: virtualhw.version = "xx"  I have: virtualhw.version = "11"   If you have minimal setup on the VSA, might be easier to re-deploy rather than trying to figure it out. If you have substantial effort put in to setting up the VSA, then we can try to dig in deeper.
So I'm stuck in service mode after having some VMware VSAN issues in my home lab. After logging into the CLI and running svc_diag, I'm presented with this error:  Rescue reason for code 0x1b30 - Virtual hardware configuration doesn't match supported profiles. Please fix configuration via hypervisor hosting the virtual machine (run "svc_diag -b" for details). SP Service Hint Code: 0xFC1B3001 - Virtual hardware configuration doesn't match supported profiles  First, I did not change anything regarding the hardware. Been running on the same hardware as before, didn't change any virtual hardware or settings regarding RAM or CPU.  Second, the command svc_diag -b does nothing, but it doesn't give me an error. It's like the command completes with no output.  At this point, I'm not sure what to do. I'm not sure which, or where the logs are at to see what is the matter. There is some output at boot, but it scrolls so fast it is impossible for me to read it, and I can't screenshot it.  Any help would be appreciated. I have some data on the array that I'd rather not lose, but if the whole thing is hosed, It's just an inconvenience.  Not sure if I can copy off my data VMDK's and present them to a newly deployed VSA and import the volumes. That would be cool if its possible. Please help!  Thanks.
Stuck in service mode after some VSAN issues.