mysql 启动报 错误：1067进程意外终止

打开错误日志，内容如下：

2017-10-25 18:40:01 10720 [Warning] Buffered warning: option 'table_definition_cache': unsigned value 200 adjusted to 400

2017-10-25 18:40:01 10720 [Note] Plugin 'FEDERATED' is disabled.
2017-10-25 18:40:01 10720 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-10-25 18:40:01 10720 [Note] InnoDB: The InnoDB memory heap is disabled
2017-10-25 18:40:01 10720 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-10-25 18:40:01 10720 [Note] InnoDB: Memory barrier is not used
2017-10-25 18:40:01 10720 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-10-25 18:40:01 10720 [Note] InnoDB: Not using CPU crc32 instructions
2017-10-25 18:40:01 10720 [Note] InnoDB: Initializing buffer pool, size = 8.0M
2017-10-25 18:40:01 10720 [Note] InnoDB: Completed initialization of buffer pool
2017-10-25 18:40:01 10720 [Note] InnoDB: Highest supported file format is Barracuda.
2017-10-25 18:40:01 10720 [Note] InnoDB: The log sequence numbers 43031231149 and 43031231149 in ibdata files do not match the log sequence number 43048830907 in the ib_logfiles!
2017-10-25 18:40:01 10720 [Note] InnoDB: Database was not shutdown normally!
2017-10-25 18:40:01 10720 [Note] InnoDB: Starting crash recovery.
2017-10-25 18:40:01 10720 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-10-25 18:40:01 10720 [Note] InnoDB: Restoring possible half-written data pages
2017-10-25 18:40:01 10720 [Note] InnoDB: from the doublewrite buffer...
2017-10-25 18:40:01 10720 [ERROR] InnoDB: We scanned the log up to 43048830464. A checkpoint was at 43048830907 and the maximum LSN on a database page was 0. It is possible that the database is now corrupt!
2017-10-25 18:40:01 2abc InnoDB: Error: page 5 log sequence number 43048830917
InnoDB: is in the future! Current system log sequence number 43048830907.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 940247808
InnoDB: Cleaning up trx with id 940246727
2017-10-25 18:40:01 2abc  InnoDB: Assertion failure in thread 10940 in file trx0trx.cc line 292
InnoDB: Failing assertion: trx->update_undo == NULL
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

将my.ini增加一行“innodb_force_recovery = 3”，重新启动服务，成功启动。