Форум пользователей MySQL

Внезапно столкнулся с тем, что служба перестала запускаться. Пишет:

121105 12:37:31 [Note] Plugin 'FEDERATED' is disabled.
121105 12:37:31 InnoDB: The InnoDB memory heap is disabled
121105 12:37:31 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121105 12:37:31 InnoDB: Compressed tables use zlib 1.2.3
121105 12:37:31 InnoDB: Initializing buffer pool, size = 47.0M
121105 12:37:31 InnoDB: Completed initialization of buffer pool
121105 12:37:31 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!
121105 12:37:31  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...
InnoDB: Error: trying to access page number 4294451583 in space 0,
InnoDB: space name D:\MySQL_Datafiles\ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
121105 12:37:33  InnoDB: Assertion failure in thread 1568 in file fil0fil.c line 4409
InnoDB: We intentionally generate a memory trap.
InnoDB: 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: http://dev.mysql.com/doc/refman/5.5/en/ … overy.html
InnoDB: about forcing recovery.
10:37:33 UTC - mysqld got exception 0xc0000005 ;
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=26214400
read_buffer_size=65536
max_used_connections=0
max_threads=100
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58327 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
terribly wrong...
603cac    mysqld.exe!my_osmaperr()
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.

Подскажите пожалуйста, как можно разрулить ситуацию?
Заранее благодарен.