MySQL从备份恢复后崩溃

我已从主机创建的备份还原了我的vserver。 此后，我的MySQL服务器不再启动

我尝试了几种方法来恢复我的表，但仍然不起作用

这就是error.log所说的：

140925 13:06:29 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140925 13:06:29 [Note] Plugin 'FEDERATED' is disabled.
140925 13:06:29 [Warning] option 'innodb-buffer-pool-size': signed value 2097152 adjusted to     5242880
140925 13:06:29 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288
140925 13:06:29 InnoDB: The InnoDB memory heap is disabled
140925 13:06:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140925 13:06:29 InnoDB: Compressed tables use zlib 1.2.3.4
140925 13:06:29 InnoDB: Initializing buffer pool, size = 5.0M
140925 13:06:29 InnoDB: Completed initialization of buffer pool
140925 13:06:29 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140925 13:06:29  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
140925 13:06:29  InnoDB: Waiting for the background threads to start
140925 13:06:30 InnoDB: Error: tablespace size stored in header is 3200 pages, but
140925 13:06:30 InnoDB: the sum of data file sizes is only 2816 pages
140925 13:06:30 InnoDB: Cannot start InnoDB. The tail of the system tablespace is
140925 13:06:30 InnoDB: missing. Have you edited innodb_data_file_path in my.cnf in an
140925 13:06:30 InnoDB: inappropriate way, removing ibdata files from there?
140925 13:06:30 InnoDB: You can set innodb_force_recovery=1 in my.cnf to force
140925 13:06:30 InnoDB: a startup if you are trying to recover a badly corrupt database.
140925 13:06:30 [ERROR] Plugin 'InnoDB' init function returned error.
140925 13:06:30 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
140925 13:06:30 [ERROR] Unknown/unsupported storage engine: InnoDB
140925 13:06:30 [ERROR] Aborting

它是一个Ubuntu 12.04服务器，具有mysql版本14.14发行版5.5.38，适用于使用readline 6.2的debian linux gnu（i686）

---

这是我尝试innodb_force_recovery=1时的日志：

您尝试过消息中可能的解决方案吗？是的，我在my.cnf中添加了innodb_force_recovery=1，但它仍然崩溃。下面是带有该选项的日志：您是如何恢复数据库的？我的服务器位于Strato（德国主机）。它提供了一个名为“备份控制”的功能，每天早上创建一个备份，最多10个备份。我使用了它的恢复功能，服务器被关闭，并被备份完全覆盖。编辑：我需要使用今天的备份，因为昨晚传来的数据。因此，不能使用昨天的备份。请询问您的主机在备份期间是否冻结了虚拟机。可能不会。他们创建了一个不一致的副本，并且您的快照不可用（状态非常类似于断电后损坏的硬盘）。您可以通过恢复部分数据，但不要指望奇迹出现。