Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > LEM fails to boot after a file system check or prompts to press Ctrl-D to continue

LEM fails to boot after a file system check or prompts to press Ctrl-D to continue

Created by Jason Dee, last modified by Justin Rouviere on Nov 09, 2016

Views: 879 Votes: 0 Revisions: 5


LEM is failing to boot after it completes a file system check and may prompt you to press Ctrl-D to continue.




All LEM versions


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


  1. Press Ctrl-D to continue if prompted.
  2. When LEM finishes booting, go to Advanced Configuration > appliance > reboot.
  3. While LEM is rebooting, observe if LEM performs another file system check or reprompts for Ctrl-D.
    1. If it reboots without a file system check, it repaired itself successfully and no further action is needed.
    2. If it performs another file system check, contact SolarWinds Support.



Last modified