Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

after loss of power,my computer restarted, and mysql can't start anymore. I use workbrench, but can't start it until I reinstal mysql server and mysql workbrench.. Please Help


140109 22:46:47 [Note] Plugin 'FEDERATED' is disabled.
140109 22:46:47 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
140109 22:46:47 InnoDB: The InnoDB memory heap is disabled
140109 22:46:47 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140109 22:46:47 InnoDB: Compressed tables use zlib 1.2.3
140109 22:46:47 InnoDB: CPU does not support crc32 instructions
140109 22:46:47 InnoDB: Initializing buffer pool, size = 56.0M
140109 22:46:47 InnoDB: Completed initialization of buffer pool
140109 22:46:47 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!
140109 22:46:47  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
140109 22:46:47 [ERROR] InnoDB:  InnoDB: Error: Attempt to open a tablespace previously opened.
Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
Cannot open tablespace sakila/actor which uses space ID: 1 at filepath: .\sakila\actor.ibd

140109 22:46:47  InnoDB: Operating system error number 997 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Error: could not open single-table tablespace file .\sakila\actor.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
share|improve this question

migrated from stackoverflow.com Jan 9 at 18:09

This question came from our site for professional and enthusiast programmers.

Any messages in the log file? –  BenM Jan 9 at 18:05
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.