# InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace

**URL:** <https://forums.percona.com/t/innodb-your-database-may-be-corrupt-or-you-may-have-copied-the-innodb-tablespace/6404>\
**Category:** Percona Server for MySQL 5.7\
**Created:** [June 9, 2018, 6:08pm UTC](https://forums.percona.com/t/innodb-your-database-may-be-corrupt-or-you-may-have-copied-the-innodb-tablespace/6404 "2018-06-09T18:08:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shrenikp7](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@shrenikp7](https://forums.percona.com/u/shrenikp7)\
**Post date:** [June 9, 2018, 6:08pm UTC](https://forums.percona.com/t/innodb-your-database-may-be-corrupt-or-you-may-have-copied-the-innodb-tablespace/6404/1 "2018-06-09T18:08:16Z")

</div>

Why every time getting following message during --prepare? Is there any way to fix it and get clean prepare?

InnoDB: Starting crash recovery.  
InnoDB: Page [page id: space=0, page number=2] log sequence number 2615513 is in the future! Current system log sequence number 2610831.  
InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to [url][http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html[/url]](http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html%5B/url%5D) for information about forcing recovery.

---

<div class="post-metadata">

**Author:** ![timureh](https://avatars.discourse-cdn.com/v4/letter/t/c2a13f/32.png) [@timureh](https://forums.percona.com/u/timureh)\
**Post date:** [July 17, 2019, 2:46am UTC](https://forums.percona.com/t/innodb-your-database-may-be-corrupt-or-you-may-have-copied-the-innodb-tablespace/6404/2 "2019-07-17T02:46:49Z")

</div>

I have the same problem…  
Did you solve this problem?

---

<div class="post-metadata">

**Author:** ![lorraine.pocklington](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lorraine.pocklington/32/37_2.png) [@lorraine.pocklington](https://forums.percona.com/u/lorraine.pocklington)\
**Post date:** [July 17, 2019, 2:57am UTC](https://forums.percona.com/t/innodb-your-database-may-be-corrupt-or-you-may-have-copied-the-innodb-tablespace/6404/3 "2019-07-17T02:57:54Z")

</div>

Hi tumureh

Could you take a look at this blog post and see if that helps you resolve your issue? [URL][https://www.percona.com/blog/2013/09/11/how-to-move-the-innodb-log-sequence-number-lsn-forward/[/URL]](https://www.percona.com/blog/2013/09/11/how-to-move-the-innodb-log-sequence-number-lsn-forward/%5B/URL%5D)

Let me know if you still need more assistance, thanks!

---

<div class="post-metadata">

**Author:** ![timureh](https://avatars.discourse-cdn.com/v4/letter/t/c2a13f/32.png) [@timureh](https://forums.percona.com/u/timureh)\
**Post date:** [July 31, 2019, 2:39am UTC](https://forums.percona.com/t/innodb-your-database-may-be-corrupt-or-you-may-have-copied-the-innodb-tablespace/6404/4 "2019-07-31T02:39:22Z")

</div>

Thanks Iorraine!

I am using a percona xtradb cluster 5.7, master - master replication, maybe in my case it is normal to receive such messages?  
I also started initialize a cluster from the backup made by the innobackupex without the use apply-logs flag. Could this affect the occurrence of such errors?

Regards.