Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My Debian (Wheezy) server has been running smoothly for a very long time with no indications of any problems. I had it running 24/7 so it was always on. The other day my power went out and when I tired to turn it back on, it freezes during it's boot process. I Googled the issue but the responses were way over my head. I am extremely new to debian/linux/unix/CLI. I booted into Ubuntu from a USB and mounted the hard drive and so I saw that all my files were there and not corrupt but I still can't boot into it normally. Below I have included a picture of what the server is saying. It stays at this screen forever.


I don't think the mount failed is the cause, that is just because I removed a hard drive that was mounted. Before I removed that drive it was still hanging at this step. Does anyone know if I can fix this? Again I am very new to all of this so if possible, try to keep everything basic.

Thank You so much!

P.S. If I am in a position that I can't fix this, could I backup the files, re-install Debian and copy the files back over?

share|improve this question
Yes, you may be able to backup your files and reinstall. Why not try booting off a livecd, to see that your files still exist, and your system works when booted from a livecd. – Zoredache Feb 4 '13 at 23:26
@Zoredache If I boot off a live Debian Cd and everything works, it there a way to just install the boot process onto my drive without re-partitioning it or formatting it? – DonJuma Feb 5 '13 at 0:58

There are several things to do with a non-booting server. If your server had been running for a while without any issues, and you have been doing updates, it is very likely that a new kernel was installed.

Additionally, if you haven't rebooted since then, it is possible that it never worked. First thing to check is if there are other options on the boot menu. When a new kernel is installed, the old is is still kept around.

There should be two options per installed kernel. One normal and one recovery. If you have an older version of the kernel you can choose, go ahead and do that (the non-recovery one). With any luck, this will resolve your issue straight away.

Failing that, the next thing to do is to go into recovery mode. If you can get to a prompt in recovery mode, it would suggest that there really is nothing serious wrong with your system and it can likely be resolved easily.

If you can't get to single user mode on one of your kernel versions, then you will have to use a recovery disk. The most likely culprit is a kernel update though and dropping back to an earlier version should fix it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.