Percona or SkySQL may be able to step in and repair it (for $$$).
For the future, switching to XtraDB (as a plugin or as included in MariaDB) may give you more resilience to such crashes.
> -----Original Message-----
> From: Larry Martell [mailto:larry.martell@stripped]
> Sent: Friday, February 01, 2013 10:49 AM
> To: mysql mailing list
> Subject: Can't drop table after crash
> We had a power hit and when the server came back we had InnoDB
> corruption. (I can't get out to the internet from the system with the
> db so can I can't paste the exact text in here). The message was about
> log sequences numbers being in the future. We were able to dump the
> affected tables, but when we tried to restore them we were not able to
> drop the old tables. When we tried the server crashed with:
> InnoDB: Failing assertion not_full_n_used >= descr_n_used
> We did try booting with innodb_force_recovery at all levels from 1 to
> 6 with the same results.
> Anyone have any ideas on what we can do to recover?
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql