Master Server stuck on boot screen



On some occasions CentOS 6 can be stuck during boot sequence.

This can happen for few reasons e.g.:

  • Corrupt system files
  • Server has run out of space on root
  • Server was shut down "forcefully" without performing graceful shutdown

                                                                                        #shutdown -h now      

This issue is separate from being stuck at Enterprise Recon startup screen


If you are getting stuck at above screen please refer to this article to rebuild your ER2 database.


If you hit the Esc key while seeing progress bar, you will switch view to display startup messages.

It should be visible from there at what point the boot is stalling, and could help to determine the cause of this issue.

If the running process is fsck, then you should wait for it to finish. This process is checking and repairing Linux filesystems.


In order to be able to look into system logs and start troubleshooting, first we need to escape the boot screen and get to command line. We do this by entering into Single User mode.

Instructions below describe this procedure:

1. Reboot your Master Server

    While booting, grub screen will be displayed, counting down the time to boot.
    At this time press any key to interrupt the auto boot.


2. ​On the following screen you will see a list operating systems installed on the machine.
    In case of multiple OS select the operating system used too boot ER2 and press “e”.


3.  On the following screen select the Kernel line (Line no: 2) and press “e” ( edit arguments ).


4. At the end of the line that will be displayed, add word “single” to enter into single user mode.
    Once added, press “Enter”.


5. You will come back to previous screen (step 3).

    Now press “b” on Kernel (Line no. 2) to boot with edited parameters.

 You should be booted in Single User mode with root privileges and see the command line



A good starting point for troubleshooting is to check available disk space on Master Server using command: df -h /


      Also check the log files:  

      /var/log/messages -generic system activity logs





You can now proceed to this article and rebuild the database



Have more questions? Submit a request


Please sign in to leave a comment.