ouia
10.10.14, 12:19
Hallo,
heute Nacht ist mein USB Stick in einem kleinem Homeserver gestorben. Hatte aber noch ein 10 Tage altes Backup. Mit aller Freude habe ich dieses auf einen anderen Stick gespielt, gestartet hatte der Server dann, aber MySQL lief nicht. Also etwas gegooglet und fsck drüber laufen lassen. Danach wieder versucht. Startet immer noch nicht. In der /var/log/mysql/error.log steht:
141010 13:15:10 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
141010 13:15:10 [Note] Plugin 'FEDERATED' is disabled.
141010 13:15:10 InnoDB: The InnoDB memory heap is disabled
141010 13:15:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141010 13:15:10 InnoDB: Compressed tables use zlib 1.2.8
141010 13:15:10 InnoDB: Using Linux native AIO
141010 13:15:10 InnoDB: Initializing buffer pool, size = 128.0M
141010 13:15:10 InnoDB: Completed initialization of buffer pool
141010 13:15:10 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 93825251
141010 13:15:10 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 93902768
141010 13:15:11 InnoDB: Error: page 2933 log sequence number 94032074
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 1261 log sequence number 94021269
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 695 log sequence number 93927872
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 2940 log sequence number 94021503
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 1269 log sequence number 94021789
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 1231 log sequence number 93987660
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 2943 log sequence number 93998279
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
kann man das irgendwie reparieren??
heute Nacht ist mein USB Stick in einem kleinem Homeserver gestorben. Hatte aber noch ein 10 Tage altes Backup. Mit aller Freude habe ich dieses auf einen anderen Stick gespielt, gestartet hatte der Server dann, aber MySQL lief nicht. Also etwas gegooglet und fsck drüber laufen lassen. Danach wieder versucht. Startet immer noch nicht. In der /var/log/mysql/error.log steht:
141010 13:15:10 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
141010 13:15:10 [Note] Plugin 'FEDERATED' is disabled.
141010 13:15:10 InnoDB: The InnoDB memory heap is disabled
141010 13:15:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141010 13:15:10 InnoDB: Compressed tables use zlib 1.2.8
141010 13:15:10 InnoDB: Using Linux native AIO
141010 13:15:10 InnoDB: Initializing buffer pool, size = 128.0M
141010 13:15:10 InnoDB: Completed initialization of buffer pool
141010 13:15:10 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 93825251
141010 13:15:10 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 93902768
141010 13:15:11 InnoDB: Error: page 2933 log sequence number 94032074
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 1261 log sequence number 94021269
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 695 log sequence number 93927872
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 2940 log sequence number 94021503
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 1269 log sequence number 94021789
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 1231 log sequence number 93987660
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
141010 13:15:11 InnoDB: Error: page 2943 log sequence number 93998279
InnoDB: is in the future! Current system log sequence number 93902768.
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.html
InnoDB: for more information.
kann man das irgendwie reparieren??