Форум пользователей MySQL

Добрый день!

Помогите пожалуйста разобраться с такой проблемой.
После восстановления системы win10 с помощью точки восстановления перестала работать база на локалхосте.


База в сборке Acquia Dev Desktop 2. В логе вот что:


151007  6:03:22 [Note] Plugin 'FEDERATED' is disabled.
151007  6:03:22 InnoDB: The InnoDB memory heap is disabled
151007  6:03:22 InnoDB: Mutexes and rw_locks use Windows interlocked functions
151007  6:03:22 InnoDB: Compressed tables use zlib 1.2.3
151007  6:03:22 InnoDB: Initializing buffer pool, size = 512.0M
151007  6:03:22 InnoDB: Completed initialization of buffer pool
151007  6:03:22 InnoDB: highest supported file format is Barracuda.
151007  6:03:24  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ … codes.html
151007  6:03:24  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\vlgbase\backup_migrate_destinations.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ … adict.html
InnoDB: for how to resolve the issue.
151007  6:03:24  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ … codes.html
151007  6:03:24  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\vlgbase\backup_migrate_profiles.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ … adict.html
InnoDB: for how to resolve the issue.
151007  6:03:24  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ … codes.html
151007  6:03:24  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\vlgbase\backup_migrate_schedules.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ … adict.html
InnoDB: for how to resolve the issue.
151007  6:03:24  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ … codes.html
151007  6:03:24  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file '.\vlgbase\backup_migrate_sources.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ … adict.html
InnoDB: for how to resolve the issue.
151007  6:03:24  InnoDB: Waiting for the background threads to start
151007  6:03:25 InnoDB: 5.5.39 started; log sequence number 1401770170
151007  6:03:25 [Note] Server hostname (bind-address): '0.0.0.0'; port: 33067
151007  6:03:25 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
151007  6:03:25 [Note] Server socket created on IP: '0.0.0.0'.
151007  6:03:25 [Note] Event Scheduler: Loaded 0 events
151007  6:03:25 [Note] C:\Program Files (x86)\DevDesktop\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.39-log'  socket: ''  port: 33067  MySQL Community Server (GPL)
InnoDB: Error: tablespace id is 2399 in the data dictionary
InnoDB: but in file .\vlgbase\cache.ibd it is 2107!
151007  6:03:26  InnoDB: Assertion failure in thread 6184 in file fil0fil.c line 768
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.5/en/ … overy.html
InnoDB: about forcing recovery.