Bonjour à tous,
J'ai récemment installé un Wamp Serveur pour mon ordi pour faire joujou avec Wordpress.
Tout se passait bien jusqu'à cette semaine. Lorsque je lance Wamp il n'arrive plus à activer tous les services.
Après analyse c'est MySQL qui déconne.
J'ai ressorti les erreurs du mysql.log:
2014-06-06 08:55:43 24060 [Note] Plugin 'FEDERATED' is disabled.
2014-06-06 08:55:44 24060 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-06 08:55:44 24060 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-06 08:55:44 24060 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-06 08:55:44 24060 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-06 08:55:44 24060 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-06-06 08:55:44 24060 [Note] InnoDB: Completed initialization of buffer pool
2014-06-06 08:55:45 24060 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-06 08:55:46 24060 [Note] InnoDB: The log sequence numbers 12893251 and 12893251 in ibdata files do not match the log sequence number 13644126 in the ib_logfiles!
2014-06-06 08:55:46 24060 [Note] InnoDB: Database was not shutdown normally!
2014-06-06 08:55:46 24060 [Note] InnoDB: Starting crash recovery.
2014-06-06 08:55:46 24060 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-06-06 08:55:48 24060 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace wordpress/wp_commentmeta uses space ID: 11 at filepath: .\wordpress\wp_commentmeta.ibd. Cannot open tablespace wordpress_creapluriel/wp_commentmeta which uses space ID: 11 at filepath: .\wordpress_creapluriel\wp_commentmeta.ibd
2014-06-06 08:55:48 1a00 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/...ror-codes.html
InnoDB: Error: could not open single-table tablespace file .\wordpress_creapluriel\wp_commentmeta.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.
La marche à suivre me parait un peu floue.
Surtout qu'il y a des éléments dans la base de données que je ne veut pas perdre.

Avez-vous eu ce problème déjà? Qu'est ce que je dois faire pour que MySQL refonctionne et que je puisse vite faire un backup de la base?

Merci d'avance pour votre aide.