You don't say why you needed to reboot this VM.
Has some serious problem occurred with the host, such as an unplanned power-down?
I would first check for a real hardware disk problem.
Try to see if you can copy the VM without any read errors, or if the copy now boots OK.
Secondly, check if the definition of the hard disk in the VM changed somehow.
Look for any wrong parameter in the VM's configuration or in its BIOS,
or perhaps the virtual disk had filled-up and needs to be enlarged,
or it could even be a corrupted disk driver in the VM.
If you have upgraded ESXi in the last 133 days, try this VM on the earlier version.
Lastly, it is entirely possible that during the last 133 days some glitch has corrupted
the VM's disk and rendered it unbootable, which you only found out now.
It that is the case, you may need to reinstall CentOS or even rebuild the VM.