Stuck in service mode after some VSAN issues.

Question

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.

AndreD Dell · Accepted Answer

Hi CFrank@Ahead,

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.

AndreD Dell · Answer

Hi CFrank@Ahead From the rescue code reason, it does look like RAM or CPU settings may have been changed (or something else). Did you check again and confirm that nothing was changed accidentally? When you say 'VMware VSAN issues in my home lab', what do you mean? What happened? Is it possible that when you tried to setup VSAN, this changed some settings for the VSA? Could you post a screen shot of the Virtual Machine Settings screen for the Unity VSA (where it shows the Memory, cores, disks)?

CFrank2 · Answer

Thanks Andre.I had power issues and my home lab and the vCenter appliance's filesystem got corrupt (outside of VSAN). So I had to rebuild&#xa0; vCenter and recreate my VDS and during that process VSAN was unavailable for a bit, which is where my UnityVSA lives. The VSA was always deployed to the VSAN datastore.Here's the screenshot. Please notice that the Virtual Machine Version is at 10, I upgraded from 9 to 10 after having issue as to try anything to fix it.At this point, network isn't even working. I think it's just hosed. I may just delete and start over, unless you guys have a smoking gun.Thanks

kelleg · Answer

Was your question answered correctly? If so, please remember to mark your question Answered when you get the correct answer and award points to the person providing the answer. This helps others searching for a similar issue.

glen

sddc_guy · Answer

if you re-created the VDC, most likely you got  new UUID fro VCenter. the VSA uses it´s UUID upon boot to set the SPA`s Serial. No chance to change afterwards. might be that your UUID in the VM Changed ? you might wabt to change it back manually

Unity

Stuck in service mode after some VSAN issues.

Was this post helpful?