Super User is a question and answer site for computer enthusiasts and power users. 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

yesterday a server of mine (debian) went into read-only mode because of problems with the main device (ext3). I contacted the hosting support and the guy told me to boot into rescue and do a fsck on the unmounted device. Lots of problems where discovered and i ended up with a messed up lost+found directory.

I tried to identify the files using "file * | grep MySQL" since i was missing a recent MySQL backup. I also did a grep searching for anything MySQL related. I noticed that the aren't any recent files in the lost+found (not even a current log).

Is there anything else to try before i re-install the server? Like an fsck option that tries harder? :)

ps: i learned that doing a fsck without doing a backup in read-only mode before was a bad idea!

share|improve this question

Your Answer


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

Browse other questions tagged or ask your own question.