Amazon error log Data 5 server crash 7-23-16

Mary Z. from Amazon emailed: I have copied part of the MySQL error log (below) from your RDS instance showing the problem that MySQL was hitting attempting to restart. The RDS Database Engineer started MySQL in “innodb_force_recover=3” and recommends to use mysqldump and restore to new RDS DB Instance to recover. As per our conversation, you could also use PiTR to recover to a point in time prior to the corruption. Please let us know if you have any further questions or concerns.=================================================================================MySQL Error Log=================================================================================InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 445566, file name mysql-bin-changelog.0955782016-07-23 18:40:41 27806 [Note] InnoDB: 128 rollback segment(s) are active. 2016-07-23 18:40:41 27806 [Note] InnoDB: Waiting for purge to start InnoDB: Starting in background the rollback of uncommitted transactions 2016-07-23 18:40:41 2ac1bb602700 InnoDB: Rolling back trx with id 619268526, 1 rows to undo 2016-07-23 18:40:41 2ac1bb602700 InnoDB: Error: Insert buffer insert fails; page free 12, dtuple size 42 InnoDB: Cannot insert index record DATA TUPLE: 2 fields; 0: len 32; hex 2020202020202020202020202020202020202020202020202020202020202020; asc ;; 1: len 4; hex 00010479; asc y;; InnoDB: The table where this index record belongs InnoDB: is now probably corrupt. Please run CHECK TABLE on InnoDB: that table. InnoDB: space 663877, page 25748, zip_size 0, bitmap bits 1 InnoDB: Submit a detailed bug report to http://bugs.mysql.com 18:40:41 UTC – mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.===============================================================================Best regards, Mary Z. Amazon Web Services