MySQL Forums
Forum List  »  Data Recovery

Re: MySQL service not starting
Posted by: Peter Brawley
Date: October 01, 2019 05:15PM

The server started with innodb_force_recovery=1?

One approach:

- find the minimum innodb_force_recovery setting that gets the server running, then ...

- mysqldump the whole shebang to a safe place, if you can ...

- run check table on every table to find corrupted tables, or ...

run mysqldump on half of the 24TB, keep cutting by half till you find the table(s) that are corrupt.

- edit corruption out of the dump(s), restore from what's left, and you'll have to regenerate what was lost to corruption.

Counter-intuitively, this works better before 5.6.16, so it may be necessary to clone the involved data folders to another drive, install 5.6.15 on another machine or drive, copy over all mysql data files, adjust my.cnf accordingly, then walk through the above.

More suggestions at ...

And institute regular backups at intervals smaller than the maximum amount of data you can afford to take time to recreate.

Options: ReplyQuote

Written By
October 01, 2019 11:26AM
October 01, 2019 02:09PM
October 01, 2019 03:03PM
October 01, 2019 03:05PM
Re: MySQL service not starting
October 01, 2019 05:15PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.