If you ever encounter an issue with the vCenter server that’s so bad that the server itself doesn’t start, well try the following:
fsck -fy /dev/mapper/log_vg-log
If it tells you that it fixed something, just press CTRL+D and let the damn thing boot.
My LAB environment’s “reliable” storage system is a Synology NAS (XPEnology actually) and I present iSCSI LUNs out of it for all my devices, including the 2x SUPER-AWESOME Supermicro SYS-5028D-TN4T that I’ve aquired in June 2016.
So, from time to time (to be read as less as possible) I reboot the NAS due to different reasons but nothing really bad happened until now as I do my homework and shutdown anything that might use that shared storage system. This time, I forgot to shutdown the vCenter server, which you guessed… was using one of the iSCSI LUNs as its underlying storage and one of the partitions got corrupted and the vCenter Server crashed and failed to boot.
Hope this helps you. I wondered a bit until figured out what’s wrong 🙂