• William B

vIDM Cluster VM Boots into Emergency Mode

Recently we needed to power off our VMware vIDM cluster nodes. I performed this operation gracefully using the vRealize Lifecycle Manager, which is the recommended option.

When the VMs rebooted, the system booted into "Emergency Mode".

Upon viewing the "journalctl" logs indicated that there had been some kind of volume corruption.

Running this command locates onboard failures which had failed:

systemctl --failed -l

This showed that there were issues with the file system on /dev/mapper/tomcat_vg-horizon.

To resolve this issue, simply run: fsck /dev/mapper/tomcat_vg-horizon and use the y option to clear the errors from the filesystem.

Enter reboot to restart the system.

The system was able to reboot successfully.