Hi Cougar281 I just experienced this same thing. There is probably a more elegant way to accomplish this but here's the process that worked for me. At the emergency mode prompt, I typed "fsck /dev/sda3" and then answered yes to all questions about repairs, inodes and fixing issues. Once the prompt was back I reset the VM and got the regular logon prompt. I then tried accessing the web interface as usual but it gave the messaage saying /vsphere-client was not available. I went back to the console, logged in as root and did a clean reboot. Once back up, I check the nifty vsphere admin page https://[vcsa-name].[domain].com:5480 and saw the health badges were green. Finally I logged in to the normal interface https://[vcsa-name].[domain].com/vsphere-client and all was well.
