Help With Corrupt MySQL Database - NEWB

[rosco]

We were running a virtual machine with the LAMP stack. We had a weird issue that took down the host. Upon restarting everything, the ubuntu machine we were running the LAMP stack on detected a corrupt disk. I restarted it and it attempted recovery. Upon bootup though, mysql will not run.

The log file under /var/log/mysql has references like this to innodb:

InnoDB: End of page dump

160215 12:03:33 InnoDB: Page checksum 2005497002, prior-to-4.0.14-form checksum 1694579326

InnoDB: stored checksum 2005497002, prior-to-4.0.14-form stored checksum 384041447

InnoDB: Page lsn 1 1892569141, low 4 bytes of lsn at page end 1892678687

InnoDB: Page number (if stored to page already) 642,

InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0

InnoDB: Page may be an insert undo log page

InnoDB: Database page corruption on disk or a failed

InnoDB: file read of page 642.

InnoDB: You may have to recover from a backup.

InnoDB: It is also possible that your operating

InnoDB: system has corrupted its own file cache

InnoDB: and rebooting your computer removes the

InnoDB: error.

InnoDB: If the corrupt page is an index page

InnoDB: you can also try to fix the corruption

InnoDB: by dumping, dropping, and reimporting

InnoDB: the corrupt table. You can use CHECK

InnoDB: TABLE to scan your table for corruption.

InnoDB: See also MySQL :: MySQL 5.5 Reference Manual :: 14.20.2 Forcing InnoDB Recovery

InnoDB: about forcing recovery.

InnoDB: Ending processing because of a corrupt database page.

160215 12:03:33 InnoDB: Assertion failure in thread 139736657061760 in file buf0buf.c line 3623

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to MySQL Bugs.

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: MySQL :: MySQL 5.5 Reference Manual :: 14.20.2 Forcing InnoDB Recovery

InnoDB: about forcing recovery.


Anyone willing to help me step by step trying to recover this data? I'm currently imaging everything over so I can try this in a test environment. Backup is too old to be useful.

Thanks!

 

[NickJames]

If that area of data is not critical, maybe try restoring only the corrupted tables from the backup to get an idea of how bad the damage is. May want to run Clonezilla while skipping bad sectors onto a clean device then attempt recovery software/sector checks on the old drive to see what's salvageable.