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 MySQL server just crashed and I cannot restart/recover it. I've tried:

/etc/init.d/mysql restart

Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!


mysqld --verbose --innodb_force_recovery=4

120528 18:44:28 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
120528 18:44:28 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
120528 18:44:28 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
120528 18:44:29  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...

both (as you can see) without success.

I've checked log files at /var/log/mysql, /var/log/mysql.err and /var/log/mysql.log but they are all empty. I don't have any other ideas. Any suggestions?

share|improve this question

Check the hardware it's running on; that could be bad ram or a bad CPU (what caused it to crash in the first place?). You might have also hit a mysql bug. You could try updating mysql (minor versions only would be my suggestion), if that's the case.

My first step would be memtest86.

share|improve this answer

This page addresses your problem exactly.

You may want to look at this MySQL page as well (for 5.0, easily you can switch to 5.1 if necessary).

I would first (server being down) remove the ib_log* files, and try a restart (remove the log files, not the data files). You may have had a log file size change - or a version change - that causes InnoDB to refuse to start.

InnoDB may sometimes be picky about log files.

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.