I had a power outage and ever since I've been unable to start the MySQL daemon. I have these errors in /var/log/mysql/error.log:
130524 20:07:43 [Note] Plugin 'FEDERATED' is disabled.
130524 20:07:43 InnoDB: The InnoDB memory heap is disabled
130524 20:07:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130524 20:07:43 InnoDB: Compressed tables use zlib 22.214.171.124
130524 20:07:43 InnoDB: Initializing buffer pool, size = 128.0M
130524 20:07:43 InnoDB: Completed initialization of buffer pool
130524 20:07:43 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130524 20:07:43 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
130524 20:07:43 InnoDB: Waiting for the background threads to start
130524 20:07:44 InnoDB: 5.5.31 started; log sequence number 72354077
130524 20:07:44 InnoDB: Assertion failure in thread 140690101622528 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
nnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATAInnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
10:07:44 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4945524 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
stack_bottom = 0 thread_stack 0x30000
130524 20:07:44 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130524 20:07:44 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130524 20:07:44 [Note] Server socket created on IP: '0.0.0.0'.
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
I'm wondering whether MySQL got corrupted when the power outage occurred. Does anyone know how to recover from something like this?