Issue – VMware vCenter Appliance 6.x crashed with a damaged LVM

Reading Time: < 1 minute

Hardware VMware Host: Fujitsu PRIMERGY RX600 S6
Hardware VMware Storage: Fujitsu ETERNUS DX90 S2
Hardware VMware vCenter Appliance: VMware vCenter Appliance 6.0
Problem: Lightning strike crashed VMware vCenter Appliance with a damaged LVM


a few days a ago I deployed my first VMware vCenter Appliance in Version 6.0. At the weekend we had a lightning strike, which caused a crash of the Appliance. So the following message appears after reboot:

Message: /dev/mapper/core_vg-core: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.


First I found this link:
So I check /dev/sda3, but that was not the problem, if I would have read it clearly. After a while I realized that the LVM has the problem. So someone give the correct hint to followed these steps:
and that worked and the vCSA was UP and RUNNING.

My steps to success:

  1. Boot the appliance to the command bash (Source:– Step “Unlocking a locked out root account”)
  2. When you on the command prompt, load the Device Mapper Module with “modprobe dm_mod
  3. Make a scan of the volume groups with “vgscan” and
  4. Activate the volume groups with “vgchange -ay
  5. Now you can make a e2fsck of the named volume group with “e2fsck -y /dev/mapper/core_vg-core” in my case
  6. CTRL-D to Exit and reboot the appliance
  7. The appliance should now UP and RUNNING




Leave a Reply

Related Post

Issue – FortiClient EMS – Upgrade to a new drive, Installers missingIssue – FortiClient EMS – Upgrade to a new drive, Installers missing

<span class="rt-reading-time" style="display: block;"><span class="rt-label rt-prefix">Reading Time: </span> <span class="rt-time">< 1</span> <span class="rt-label rt-postfix">minute</span></span> Hardware VMware Host: Fujitsu PRIMERGY RX2450 M1Hardware VMware Storage: Fujitsu ETERNUS DX200Software VMware vCenter Appliance: VMware vCenter Appliance 6.0Software FortiClient EMS: 6.0.4Problem: FortiClient EMS

%d bloggers like this: