Не удалось запустить MySQL-5.6 на Openserver

OpenServer 5.2.2 В этот прекрасный день отказался запускаться.

   2017-09-30 11:02:39  --------------------------------------------
2017-09-30 11:02:39  Начало процедуры запуска сервера
2017-09-30 11:02:39  Обновление Hosts файла
2017-09-30 11:02:39  Обновление конфигурации MySQL-5.6
2017-09-30 11:02:39  Обновление конфигурации Sendmail
2017-09-30 11:02:39  Обновление конфигурации PHP-5.6
2017-09-30 11:02:39  Обновление конфигурации PHPMyAdmin
2017-09-30 11:02:39  Обновление конфигурации Apache-2.4+Nginx-1.10
2017-09-30 11:02:39  Запуск MySQL-5.6
2017-09-30 11:02:39  Запуск Apache-2.4+Nginx-1.10
2017-09-30 11:02:39  Проверка состояния сервера
2017-09-30 11:03:13  Не удалось запустить MySQL-5.6
2017-09-30 11:03:13  Сбой запуска!
2017-09-30 11:03:13  --------------------------------------------
2017-09-30 11:03:13  Начало процедуры остановки сервера
2017-09-30 11:03:13  Остановка системных модулей
2017-09-30 11:03:13  Отключение виртуального диска
2017-09-30 11:03:13  Сервер успешно остановлен за 0,218 секунд!

 2017-09-30 11:02:39 0 [Note] c:\ospanel\modules\database\MySQL-5.6\bin\mysqld.exe (mysqld 5.6.37) starting as process 3236 ...
    2017-09-30 11:02:39 3236 [Note] Plugin 'FEDERATED' is disabled.
    2017-09-30 11:02:39 3236 [Note] MyISAM: Using atomics to ref count buffer pool pages
    2017-09-30 11:02:39 3236 [Note] MyISAM: The MyISAM memory heap is disabled
    2017-09-30 11:02:39 3236 [Note] MyISAM: Mutexes and rw_locks use Windows interlocked functions
    2017-09-30 11:02:39 3236 [Note] MyISAM: Memory barrier is not used
    2017-09-30 11:02:39 3236 [Note] MyISAM: Compressed tables use zlib 1.2.3
    2017-09-30 11:02:39 3236 [Note] MyISAM: Not using CPU crc32 instructions
    2017-09-30 11:02:39 3236 [Note] MyISAM: Initializing buffer pool, size = 128.0M
    2017-09-30 11:02:39 3236 [Note] MyISAM: Completed initialization of buffer pool
    2017-09-30 11:02:39 3236 [Note] MyISAM: Highest supported file format is Barracuda.
    2017-09-30 11:02:39 3236 [Note] MyISAM: The log sequence numbers 4372925 and 4372925 in ibdata files do not match the log sequence number 4372935 in the ib_logfiles!
    2017-09-30 11:02:39 3236 [Note] MyISAM: Database was not shutdown normally!
    2017-09-30 11:02:39 3236 [Note] MyISAM: Starting crash recovery.
    2017-09-30 11:02:39 3236 [Note] MyISAM: Reading tablespace information from the .ibd files...
    2017-09-30 11:02:39 e98  MyISAM: Operating system error number 2 in a file operation.
    MyISAM: Some operating system error numbers are described at
    MyISAM: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
    MyISAM: Error: could not open single-table tablespace file .\ther.ibd
    MyISAM: We do not continue the crash recovery, because the table may become
    MyISAM: corrupt if we cannot apply the log records in the MyISAM log to it.
    MyISAM: To fix the problem and start mysqld:
    MyISAM: 1) If there is a permission problem in the file and mysqld cannot
    MyISAM: open the file, you should modify the permissions.
    MyISAM: 2) If the table is not needed, or you can restore it from a backup,
    MyISAM: then you can remove the .ibd file, and MyISAM will do a normal
    MyISAM: crash recovery and ignore that table.
    MyISAM: 3) If the file system or the disk is broken, and you cannot remove
    MyISAM: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
    MyISAM: and force MyISAM to continue crash recovery here.