vCenter appliance boot to emergency mode due to a corrupted file system
After I had to restart vCenter for some reason, this server failed to boot properly and went into the Emergency Mode. The appliance fails to start and reports the following message:
To find out the root cause of this error, open the vCenter Console and scroll up (Shift + Page Up) the screen to see the first error. As you can see, one of the partitions “/dev/core_vg/core” is corrupted and it’s filesystem needs to be checked.
First, check that none of your filesystems are full, enter the root password and type shell to access the bash shell and then type “df –h” command to show filesystems usage. As you can see, none of the filesystems are full.
So let’s run a filesystem check on /dev/core_vg/core. You can answer all questions manually or use the “-y” option to automatically fix all issues. Unfortunately, I forgot to take a photo of this stage.
When the filesystem has been fixed, reboot vCenter.
Now you should be able to boot the vCenter Service Appliance properly.
For those who are not reading all the comments, if you, like some people, are unable to scroll through the console port or experiencing difficulty in identifying the root cause of the problem like some guys, I recommend redirecting boot errors to a virtual serial port file as a solution.