Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
Updated June 18, 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.
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:
b. Run fsck to the affected partition.
For example: Each of the commands below will run fsck and repair the mentioned partition"
d. Run the following commands:
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.