Bug #78849 corruption in the InnoDB tablespace (server failed to start)
Submitted: 15 Oct 2015 20:44 Modified: 24 Sep 2018 16:30
Reporter: Allen Shu Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.6 OS:Microsoft Windows (7)
Assigned to: Bogdan Kecman CPU Architecture:Any
Tags: innodb, recovery

[15 Oct 2015 20:44] Allen Shu
Description:
My server failed to start due to an InnoDB error (log as below). I tried to follow the suggested solutions at "http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html" but still fail to restart my server. Any hints will be appreciated.

Error message in log file:
FROM USER-PC.err:
    2015-10-15 09:01:50  4712  Note  Plugin 'FEDERATED' is disabled.
    2015-10-15 09:01:50  4712  Warning  option 'innodb-autoextend-increment': unsigned value 67108864 adjusted to 1000
          2015-10-15 09:01:50 f14 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.
    2015-10-15 09:01:50  4712  Note  InnoDB: Using atomics to ref count buffer pool pages
    2015-10-15 09:01:50  4712  Note  InnoDB: The InnoDB memory heap is disabled
    2015-10-15 09:01:50  4712  Note  InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2015-10-15 09:01:50  4712  Note  InnoDB: Memory barrier is not used
    2015-10-15 09:01:50  4712  Note  InnoDB: Compressed tables use zlib 1.2.3
    2015-10-15 09:01:50  4712  Note  InnoDB: Not using CPU crc32 instructions
    2015-10-15 09:01:50  4712  Note  InnoDB: Initializing buffer pool, size = 143.0M
    2015-10-15 09:01:50  4712  Note  InnoDB: Completed initialization of buffer pool
    2015-10-15 09:01:50  4712  Note  InnoDB: Highest supported file format is Barracuda.
    2015-10-15 09:01:50  4712  Note  InnoDB: The log sequence numbers 36396263 and 36396263 in ibdata files do not match the log sequence number 36643967 in the ib_logfiles!
    2015-10-15 09:01:50  4712  Note  InnoDB: Database was not shutdown normally!
    2015-10-15 09:01:50  4712  Note  InnoDB: Starting crash recovery.
    2015-10-15 09:01:50  4712  Note  InnoDB: Reading tablespace information from the .ibd files...
    2015-10-15 09:01:50  4712  Note  InnoDB: Restoring possible half-written data pages 
    2015-10-15 09:01:50  4712  Note  InnoDB: from the doublewrite buffer...
    2015-10-15 09:01:50  4712  Note  InnoDB: 128 rollback segment(s) are active.
    2015-10-15 09:01:50  4712  Note  InnoDB: Waiting for purge to start
          2015-10-15 09:01:50 14dc  InnoDB: Assertion failure in thread 5340 in file trx0purge.cc line 699
          InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
          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.6/en/forcing-innodb-recovery.html
          InnoDB: about forcing recovery.
    2015-10-15 09:01:50  4712  Note  InnoDB: 5.6.26 started; log sequence number 36643967
    2015-10-15 09:01:50  4712  Note  Server hostname (bind-address): '*'; port: 3306
    2015-10-15 09:01:50  4712  Note  IPv6 is available.
    2015-10-15 09:01:50  4712  Note    - '::' resolves to '::';
    2015-10-15 09:01:50  4712  Note  Server socket created on IP: '::'.
    2015-10-15 09:01:50  4712  Note  Event Scheduler: Loaded 0 events
    2015-10-15 09:01:50  4712  Note  C:/Program Files/MySQL/MySQL Server 5.6/bin\mysqld: ready for connections.
          Version: '5.6.26-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
2015-10-15 09:01:54 - Checking server status...
2015-10-15 09:01:54 - Trying to connect to MySQL...
2015-10-15 09:01:54 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2015-10-15 09:01:54 - Assuming server is not running
2015-10-15 09:01:54 - Checking server status...
2015-10-15 09:01:54 - Trying to connect to MySQL...
2015-10-15 09:01:54 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2015-10-15 09:01:54 - Assuming server is not running

How to repeat:
corruption in the InnoDB tablespace
[24 Sep 2018 16:30] Bogdan Kecman
Hi Allen,

I don't have enough data to reproduce this. I assume you did prevent any antivirus/antimalware software to mess with your MySQL datadir? And that you do not have any malware on your system?

kind regards
Bogdan