Vcenter in Ermergency mode with error "Failed to start File System Check on /dev/vg_root_0/lv_root_0"

Products

• VMware vCenter Server

Issue/Introduction

After a storage outage event, a vCenter may fail to boot with the error message "Failed to start File System Check on /dev/vg_root_0/lv_root_0".

Or you may see a message indicating a specific directory, such as /storage/log.

Environment

vCenter 7.x
vCenter 8.x

Cause

• This issue occurs when the virtual appliance experiences file inconsistencies after being forcefully halted as the result of a storage failure, power failure, or other crash.

Resolution

Before making any changes, take a powered off snapshot of vCenter or a backup.  If vCenter is linked to another vCenter using Enhanced Linked Mode take a powered off snapshot of all linked vCenters.  

• Use the steps outlined for the fsck command, as described in this KB: Error: Failed to start Network Service.

# fsck -fy /dev/vg_root_0/lv_root_0
# reboot

Or

• Use the steps outlined for the e2fsck command, as described in this KB: Manually running a filesystem check.

# e2fsck -y /dev/vg_root_0/lv_root_0
# reboot

Additional Information

In some cases there may be multiple partitions causing the Vcenter to enter emergency mode

Run  journalctl from root of vCenter , to identify the failing partition.

example : /dev/vg_root_0/lv_root_0 as the affected volume.

Executed filesystem repair using below commands as described in resolution section.

fsck -fy /dev/vg_root_0/lv_root_0

or

e2fsck -y /dev/vg_root_0/lv_root_0

Rebooted the appliance after each repair attempt.

The appliance may reboot multiple times during this process as it resolves underlying filesystem issues. Monitoring continues to ensure stability post-repair.