Fix corrupted InnoDB

Dedicated server at [url removed, login to view] crashed. They moved everything to a newly installed server, but now we cannot access the databases. Support at [url removed, login to view] says that we need to have someone fix the corrupted innodb. Below is a response from the data center:

"In the /etc/[url removed, login to view] file, these two values are not valid:

skip-locking

set-variable = max_connections=500

This is indicated in the MySQL error log at /var/lib/mysql/[url removed, login to view]:

150511 14:18:54 [ERROR] /usr/sbin/mysqld: unknown variable 'set-variable=max_connections=500'

150511 14:19:29 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.

I did comment out those entries in /etc/my.cnf. That did not fix the issue with MySQL starting, however I just wanted to bring it to your attention.

The reason that MySQL will not start is because with a issue with InnoDB:

150511 14:19:30 InnoDB: Starting shutdown...

150511 14:19:30 InnoDB: Error: page 451 log sequence number 767171019

InnoDB: is in the future! Current system log sequence number 1570935.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: [url removed, login to view]

InnoDB: for more information.

150511 14:19:30 InnoDB: Error: page 452 log sequence number 766961791

InnoDB: is in the future! Current system log sequence number 1570935.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: [url removed, login to view]

InnoDB: for more information.

150511 14:19:30 InnoDB: Error: page 331 log sequence number 767252881

InnoDB: is in the future! Current system log sequence number 1570935.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: [url removed, login to view]

InnoDB: for more information.

150511 14:19:30 InnoDB: Error: page 55 log sequence number 767159435

InnoDB: is in the future! Current system log sequence number 1570935.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: [url removed, login to view]

InnoDB: for more information.

150511 14:19:30 InnoDB: Error: page 374 log sequence number 767389785

InnoDB: is in the future! Current system log sequence number 1570935.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: [url removed, login to view]

InnoDB: for more information.

150511 14:19:30 InnoDB: Error: page 369 log sequence number 767389763

InnoDB: is in the future! Current system log sequence number 1570935.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: [url removed, login to view]

InnoDB: for more information.

150511 14:19:30 InnoDB: Shutdown completed; log sequence number 1570935

150511 14:19:30 [Note] /usr/sbin/mysqld: Shutdown complete

Please review the information in the InnoDB Corruption Repair Guide at our forums:

[url removed, login to view]

I would however strongly suggesting consulting with a database/system administrator as InnoDB recovery is outside of the support we provide."

Data Center says:
Hello Joseph,

The DBA will need to SSH into the server to fix mySQL. Once they fix it, mysql will be online.
--
Andrew Zahn
System Administrator
www.singlehop.com
500 W. Madison St. Suite #800
Office: 1-866-817-2811 x341
Local: 1-312-447-2580 x341

Databaseadministrasjon MySQL

Prosjekt-ID: #7651997

Om prosjektet