求助，mysql在机器raid控制器出意外后，无法重启

lingy

mysql。err的log
081017 13:43:33  mysqld started
081017 13:43:33  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...
081017 13:43:33  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 2316551305.
InnoDB: Doing recovery: scanned up to log sequence number 2 2316560700
081017 13:43:33  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 mysqld got signal 11;
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.

key_buffer_size=0
read_buffer_size=16773120
max_used_connections=0
max_connections=1500
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 122873988 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
081017 13:43:33  mysqld ended


请问怎么修复，谢谢

yueliangdao0608

Only these information can help you solving your problem.


key_buffer_size=0
read_buffer_size=16773120
max_used_connections=0
max_connections=1500
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 122873988 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
[color]