Mysql批处理闪退，错误代码如下

jkewajj

1小时前还好好的，不知怎么回事，现在点击
启动MySQL数据库.bat
就会闪退。。。。。启动不了数据库
在CMD命令中 启动，错误代码如下：
备注：另外一个文件夹下的wex5  数据库可以正常启动

1. 2017-11-19 04:10:02 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
   
2. 2017-11-19 04:10:02 0 [Note] mysqld (mysqld 5.6.26) starting as process 17644 ...
   
3. 2017-11-19 04:10:02 17644 [Note] Plugin 'FEDERATED' is disabled.
   
4. 2017-11-19 04:10:02 17644 [Note] InnoDB: Using atomics to ref count buffer pool pages
   
5. 2017-11-19 04:10:02 17644 [Note] InnoDB: The InnoDB memory heap is disabled
   
6. 2017-11-19 04:10:02 17644 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
   
7. 2017-11-19 04:10:02 17644 [Note] InnoDB: Memory barrier is not used
   
8. 2017-11-19 04:10:02 17644 [Note] InnoDB: Compressed tables use zlib 1.2.3
   
9. 2017-11-19 04:10:02 17644 [Note] InnoDB: Not using CPU crc32 instructions
   
10. 2017-11-19 04:10:02 17644 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    
11. 2017-11-19 04:10:02 17644 [Note] InnoDB: Completed initialization of buffer pool
    
12. 2017-11-19 04:10:02 17644 [Note] InnoDB: Highest supported file format is Barracuda.
    
13. 2017-11-19 04:10:02 17644 [Note] InnoDB: The log sequence numbers 2298468 and 2298468 in ibdata files do not match the log sequence number 3877777 in the ib_logfiles!
    
14. 2017-11-19 04:10:02 17644 [Note] InnoDB: Database was not shutdown normally!
    
15. 2017-11-19 04:10:02 17644 [Note] InnoDB: Starting crash recovery.
    
16. 2017-11-19 04:10:02 17644 [Note] InnoDB: Reading tablespace information from the .ibd files...
    
17. 2017-11-19 04:10:02 44f0  InnoDB: Operating system error number 2 in a file operation.
    
18. InnoDB: Some operating system error numbers are described at
    
19. InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    
20. InnoDB: Error: could not open single-table tablespace file .\dem.ibd
    
21. InnoDB: We do not continue the crash recovery, because the table may become
    
22. InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
    
23. InnoDB: To fix the problem and start mysqld:
    
24. InnoDB: 1) If there is a permission problem in the file and mysqld cannot
    
25. InnoDB: open the file, you should modify the permissions.
    
26. InnoDB: 2) If the table is not needed, or you can restore it from a backup,
    
27. InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
    
28. InnoDB: crash recovery and ignore that table.
    
29. InnoDB: 3) If the file system or the disk is broken, and you cannot remove
    
30. InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
    
31. InnoDB: and force InnoDB to continue crash recovery here.

复制代码

liangyongfei

自己百度搜下这个错误的日志
试试网上提供的解决方法吧！

http://www.jb51.net/article/71052.htm
http://blog.csdn.net/jackqn/article/details/50357497

wex5 自带的mysql 也是标准mysql数据库