Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

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

In my office I've Ubuntu 8.10 desktop installed and it's running for a long time. When ever the system is started, I'll get a file system maintenance error and something it's prompted for the root password or (press ctrl+d to continue). After pressing Ctrl+D the system normally boots up. I could not resolve this issue for a long time and I think something should be done in the fstab file. I'm not sure to do anything and expecting the experts here to help to perfectly fix this. Any help is appreciated.


share|improve this question
Post the output of cat /etc/fstab – karthick87 Jan 2 '11 at 6:58
I'll definitely post it but at later time as I'm not at that system right now. – user3215 Jan 2 '11 at 7:15
Run: fsck -A -y , post the output. – João Pinto Jan 2 '11 at 23:09
fsck fixed the issue but I think there may be other way to do this as fsck itself corrupt the fs while recovering. – user3215 Jan 17 '11 at 12:08
I don't think there is another way to do this, but I'd love to hear about it if there is.... – belacqua Feb 4 '11 at 3:43
up vote 3 down vote accepted

This happens when the root (/) filesystem gets corrupt and needs to be fixed. At the point during the boot where it finds that the root filesystem is corrupt, the root filesystem is already mounted, and Ubuntu won't do a fsck on a filesystem that is mounted since that is unsafe.

The best way to recover from this is to boot the liveCD and run a filesystem check on it from there, when it is not mounted. You can use fsck from a terminal, or run gparted (in System -> Administration) where you can right-click the filesystem and choose "check".

Also, please note that Ubuntu 8.10 Desktop is no longer supported. You should upgrade to a supported version. See for help on how to do that.

share|improve this answer
One should be cautious as fsck may also corrupt the fs on a way to recovery. – user3215 Jan 22 '11 at 1:40

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.