MySQL Bugs: #89106: Server is crashing due to Failing assertion

Bug #89106	Server is crashing due to Failing assertion
Submitted:	4 Jan 2018 13:05	Modified:	5 Jan 2018 12:25
Reporter:	Michel Legere	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Windows	Severity:	S1 (Critical)
Version:	5.6	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
2018-01-03 22:46:13 c28  InnoDB: Assertion failure in thread 3112 in file btr0cur.cc line 297
InnoDB: Failing assertion: btr_page_get_prev(get_block->frame, mtr) == page_get_page_no(page)
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.

How to repeat:
server can't start

Did you read and try the error message: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html ?.

no not at all. i have 5 schema and 3 of them i was able to dump and backup.( not tested yet). the 4th one witch is 1.2 Gb, i was able to run the MySQL service with innodb_force_recovery = 3 and backup the database. the 5th schema , it's folder is 250G in the programdata/data/ folder, i can't dump an any innodb_force_recovery 1 to 6. i don't know what to do next, can you help me? i have a database offline for 4 days for a hospital because of this.

sorry i meant "not at all" as it is not working. and to answer your question, as you can see in the comments yes i did try innodb_force_recovery ( all day)

I see you have already attempted innodb_force_recovery 1 to 6, a value of 4 or greater is considered dangerous because data files can be permanently corrupted. A value of 6 is considered drastic because database pages are left in an obsolete state, which in turn may introduce more corruption into B-trees and other database structures.

Imho, If corruption within the table data prevents you from dumping the entire table contents, a query with an ORDER BY primary_key DESC clause might be able to dump the portion of the table after the corrupted part.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/