江湖救急 mysql 启动不起

歪歪 2015-05-14 01:55:42

150514 13:17:52 [Note] Plugin 'FEDERATED' is disabled.
150514 13:17:52 [Note] Plugin 'InnoDB' is disabled.
150514 13:17:52 [ERROR] Unknown/unsupported storage engine: INNODB
150514 13:17:52 [ERROR] Aborting

150514 13:17:52 [Note] D:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete

150514 13:19:20 [Note] Plugin 'FEDERATED' is disabled.
150514 13:19:20 InnoDB: The InnoDB memory heap is disabled
150514 13:19:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
150514 13:19:20 InnoDB: Compressed tables use zlib 1.2.3
150514 13:19:20 InnoDB: Initializing buffer pool, size = 10.0G
150514 13:19:21 InnoDB: Completed initialization of buffer pool
150514 13:19:21 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1532524876909
150514 13:19:21 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: Doing recovery: scanned up to log sequence number 1532530119680
InnoDB: Doing recovery: scanned up to log sequence number 1532535362560
InnoDB: Doing recovery: scanned up to log sequence number 1532540605440
InnoDB: Doing recovery: scanned up to log sequence number 1532543344508
150514 13:19:28 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 2255, file name .\binLog.000493
150514 13:20:07 InnoDB: Waiting for the background threads to start
150514 13:20:08 InnoDB: 1.1.6 started; log sequence number 1532543344508
150514 13:20:08 [Note] Recovering after a crash using binLog
150514 13:20:08 [Note] Starting crash recovery...
150514 13:20:08 [Note] Crash recovery finished.
150514 13:20:08 [Note] Event Scheduler: Loaded 1 event
150514 13:20:08 [Note] D:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.11-log' socket: '' port: 3306 MySQL Community Server (GPL)
150514 13:20:10 InnoDB: Assertion failure in thread 6936 in file ..\..\..\mysql-5.5.11\storage\innobase\trx\trx0purge.c line 828
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
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/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
150514 13:20:10 - 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=524288000
read_buffer_size=131072
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 = 1754624 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...
000000013F7BFCFC mysqld.exe!my_osmaperr()
000000013F7BFED0 mysqld.exe!my_osmaperr()
000000013F7C0091 mysqld.exe!my_osmaperr()
000000013F844B29 mysqld.exe!my_osmaperr()
000000013F844C28 mysqld.exe!my_osmaperr()
000000013F824B39 mysqld.exe!my_osmaperr()
000000013F825140 mysqld.exe!my_osmaperr()
000000013F8252CF mysqld.exe!my_osmaperr()
000000013F7C04B6 mysqld.exe!my_osmaperr()
000000013F7AE1E1 mysqld.exe!my_osmaperr()
000000013F7AE722 mysqld.exe!my_osmaperr()
0000000076AD59ED kernel32.dll!BaseThreadInitThunk()
0000000076E4C541 ntdll.dll!RtlUserThreadStart()
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.
InnoDB: Thread 7200 stopped in file ..\..\..\mysql-5.5.11\storage\innobase\os\os0sync.c line 474
InnoDB: Thread 6612 stopped in file ..\..\..\mysql-5.5.11\storage\innobase\os\os0sync.c line 813

...全文