Dear MRatWork,
i already change it to #skip-innodb, and did service mysqld restart, now it show Got error -1 from storage engine.
this is
tail -100 /var/log/mysqld.logInnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:33 InnoDB: Error: page 19561 log sequence number 48165464201
InnoDB: is in the future! Current system log sequence number 9419.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:33 InnoDB: Error: page 19562 log sequence number 48165464216
InnoDB: is in the future! Current system log sequence number 9419.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:33 InnoDB: Error: page 19559 log sequence number 48165464251
InnoDB: is in the future! Current system log sequence number 9419.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:33 InnoDB: Error: page 40019 log sequence number 48166426182
InnoDB: is in the future! Current system log sequence number 9419.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:35 InnoDB: Error: page 19691 log sequence number 31982746099
InnoDB: is in the future! Current system log sequence number 9419.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:35 InnoDB: Error: page 26600 log sequence number 7285548658
InnoDB: is in the future! Current system log sequence number 9419.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:35 InnoDB: Error: page 13284 log sequence number 48120571499
InnoDB: is in the future! Current system log sequence number 9419.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:35 InnoDB: Error: page 26598 log sequence number 30032196393
InnoDB: is in the future! Current system log sequence number 9429.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:37 InnoDB: Error: page 32563 log sequence number 14120
InnoDB: is in the future! Current system log sequence number 9429.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:37 InnoDB: Error: page 15309 log sequence number 15566
InnoDB: is in the future! Current system log sequence number 9429.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
170613 16:47:37 InnoDB: Error: page 32191 log sequence number 15566
InnoDB: is in the future! Current system log sequence number 9429.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
170613 16:47:39 InnoDB: Error: page 32082 log sequence number 48165406681
InnoDB: is in the future! Current system log sequence number 9429.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlInnoDB: for more information.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
If i change to #innodb_force_recovery=1 and did service mysqld restart, it show
MySQL Daemon failed to start.