Since then I get the following at my logfile:
2018-01-13 17:55:53 10116 [Note] Plugin 'FEDERATED' is disabled.
2018-01-13 17:55:53 2340 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.
2018-01-13 17:55:53 10116 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-01-13 17:55:53 10116 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-13 17:55:53 10116 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-01-13 17:55:53 10116 [Note] InnoDB: Memory barrier is not used
2018-01-13 17:55:53 10116 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-13 17:55:53 10116 [Note] InnoDB: Not using CPU crc32 instructions
2018-01-13 17:55:53 10116 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2018-01-13 17:55:53 10116 [Note] InnoDB: Completed initialization of buffer pool
2018-01-13 17:55:53 10116 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-13 17:55:53 10116 [Note] InnoDB: The log sequence numbers 92733888955 and 92733888955 in ibdata files do not match the log sequence number 92733888965 in the ib_logfiles!
2018-01-13 17:55:53 10116 [Note] InnoDB: Database was not shutdown normally!
2018-01-13 17:55:53 10116 [Note] InnoDB: Starting crash recovery.
2018-01-13 17:55:53 10116 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-01-13 17:55:54 10116 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace e/account_child uses space ID: 35 at filepath: .\e\account_child.ibd. Cannot open tablespace eclinic/account_child which uses space ID: 35 at filepath: .\eclinic\account_child.ibd
InnoDB: Error: could not open single-table tablespace file .\eclinic\account_child.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.
2018-01-13 18:09:13 4060 [Note] Plugin 'FEDERATED' is disabled.
Solution:
1. You Must Enable innodb_force_recovery option.
2. Edit my.cnf - Add the line: # innodb_force_recovery = 2
3. Restart MySQL Service(MySQL engine repair itself)
4. Comment the innodb_force_recovery line in My.cng file
5. Restart MySQL again
6. Now Mysql started
Video Tutorial:
2018-01-13 17:55:53 10116 [Note] Plugin 'FEDERATED' is disabled.
2018-01-13 17:55:53 2340 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.
2018-01-13 17:55:53 10116 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-01-13 17:55:53 10116 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-13 17:55:53 10116 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-01-13 17:55:53 10116 [Note] InnoDB: Memory barrier is not used
2018-01-13 17:55:53 10116 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-13 17:55:53 10116 [Note] InnoDB: Not using CPU crc32 instructions
2018-01-13 17:55:53 10116 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2018-01-13 17:55:53 10116 [Note] InnoDB: Completed initialization of buffer pool
2018-01-13 17:55:53 10116 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-13 17:55:53 10116 [Note] InnoDB: The log sequence numbers 92733888955 and 92733888955 in ibdata files do not match the log sequence number 92733888965 in the ib_logfiles!
2018-01-13 17:55:53 10116 [Note] InnoDB: Database was not shutdown normally!
2018-01-13 17:55:53 10116 [Note] InnoDB: Starting crash recovery.
2018-01-13 17:55:53 10116 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-01-13 17:55:54 10116 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace e/account_child uses space ID: 35 at filepath: .\e\account_child.ibd. Cannot open tablespace eclinic/account_child which uses space ID: 35 at filepath: .\eclinic\account_child.ibd
InnoDB: Error: could not open single-table tablespace file .\eclinic\account_child.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.
2018-01-13 18:09:13 4060 [Note] Plugin 'FEDERATED' is disabled.
Solution:
1. You Must Enable innodb_force_recovery option.
2. Edit my.cnf - Add the line: # innodb_force_recovery = 2
3. Restart MySQL Service(MySQL engine repair itself)
4. Comment the innodb_force_recovery line in My.cng file
5. Restart MySQL again
6. Now Mysql started
Video Tutorial:
0 Comments