Bonjour.
Je travaille avec easy php 13.1 (oui c'est pas la dernière) le logiciel est lancé sur une clé USB.
MYSQL 5.6.11
Pendant que je modifiais ma BDD, l'ordinateur n'a plus reconnu la clé et le serveur de BDD a planté.
Si j'essaie de le redémarrer, j'ai le message suivant :
"Unespected end of Mysql...See log Files ?"
Le log file, c'est :
2017-10-09 16:54:11 13240 [Note] Plugin 'FEDERATED' is disabled.
2017-10-09 16:54:11 2c10 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.
2017-10-09 16:54:11 13240 [Note] InnoDB: The InnoDB memory heap is disabled
2017-10-09 16:54:11 13240 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-10-09 16:54:11 13240 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-10-09 16:54:11 13240 [Note] InnoDB: Not using CPU crc32 instructions
2017-10-09 16:54:11 13240 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-10-09 16:54:11 13240 [Note] InnoDB: Completed initialization of buffer pool
2017-10-09 16:54:11 13240 [Note] InnoDB: Highest supported file format is Barracuda.
2017-10-09 16:54:11 13240 [Note] InnoDB: The log sequence numbers 10698783 and 10698783 in ibdata files do not match the log sequence number 10698793 in the ib_logfiles!
2017-10-09 16:54:11 13240 [Note] InnoDB: Database was not shutdown normally!
2017-10-09 16:54:11 13240 [Note] InnoDB: Starting crash recovery.
2017-10-09 16:54:11 13240 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-10-09 16:54:11 13240 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace touslesport/multisports which uses space ID: 1 at filepath: .\touslesport\multisports.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\multisports.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.
Il y là une foule d'info (en anglais, donc que traduis mal).
Je travaillais sur une BDD qui s'appelle touslesport.V2 et pas touslesport.
Je travaillais sur une autre table que multisports.

Comment puis-je récupérer ma structure et mes données ?

Merci de votre aide.