We have a server running MySQL and a lot of databases.
The server had an unexpected outage, followed by a corrupted disk.
FSCK seemed to solve the problem, and got it up and running again.
However MySQL had an issue, which at first simply seemed to be a permissions issue.
MySQL would no longer start up ("Manager of pid-file quit without updating fi").
Log says that MySQL got signal 11 and crashed.
This could be helped by adding "skip-innodb" to the [url removed, login to view] configuration.
Then MySQL server runs fine.
We do have a couple of InnoDB databases we would like to restore.
Moving them to a fresh server does not help - service startup times out, and log reveals the same (signal 11).
Bid if you think you can solve this problem.
PM me with some details regarding your plan of action, so I know that you know what you're doing and have a clue at all.
11 freelancers are bidding on average $32/hour for this job
Hello, I am experienced linux administrator and I have been solving with such issues related with InnoDB. It will be pleasure to me to work with you and help for solving your problem.
I'm experienced in innodb recovery with or without working innodb engine (directly from datafiles) as well as C programming (which could be helpfull to workarounds some of restrictions of recovery tools)