vIDM Cluster VM Boots into Emergency Mode
- William B
- Sep 27, 2022
- 1 min read
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 -lThis 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.
For technical teams, a Merge PDF tool can also be helpful when dealing with troubleshooting documentation. Logs, configuration notes, recovery procedures, screenshots, and related guides are often stored as separate
PDF files, making them harder to review together. Combining those documents into one PDF creates a more convenient reference that can be shared with colleagues or kept alongside a project for future incidents. It is a simple way to turn scattered technical resources into one organized document.