Submit a ticketCall us

WebinarUpcoming Webinar: Easily Automate Backups and Simplify Log Message Management

Backing up your network configuration and logging data are a few steps to helping keep your network safe. In this in-depth webinar, we’ll show you how these tasks can be automated to save your IT team time while maintaining accurate archives of your data.

Register now.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Error: Unexpected inconsistency - fsck died with exit status 4

Error: Unexpected inconsistency - fsck died with exit status 4

Updated July 18th, 2016


This article describes the issue when you receive the following error when LEM appliance has been restarted and you are unable to log in to the LEM Console.

Error: Unexpected inconsistency - fsck died with exit status 4



LEM version 6.2


The file system on LEM has become corrupted due to improper appliance shutdown or loss of power on the VM host.


  1. Reboot LEM (cmc: appliance > reboot) to force a file system check.
  2. Within the error that says Give root password for maintenance (or type Control-D to continue), enter the root password (ROOT password must be entered by Solarwinds tech support).
  3. Once you have logged in as root, run the following commands:

a. Change the runlevel by logging in to the vSphere or Hyper V console and entering: init 1 

This allows for unmounting partitions. Mount, umount can be used to unmount.

For example: A filesystem can be unmounted with the following:
                umount /dev/sda5
b. Run fsck to the affected partition. 

For example: Each of the commands below will run fsck and repair the mentioned partition"

  • fsck -y /dev/sda1
  • fsck -y /dev/sda2
  • fsck -y /dev/sda5
  • fsck -y /dev/sda6?

d.  Run the following commands:

  • fsck -y /dev/sda2
  • fsck -y /dev/sda5

Note: fsck must run with unmounted partitions.


e. Change run level back to normal operation if the fsck completes successfully by entering: init 6

After performing both of the fsck manually in the mentioned partitions above and running reboot command under cmc (cmc: appliance > reboot), this should now continue without any errors. 



Last modified