innodb sorunu

Sunucuda bulunan sitelerim sürekli innodb log oluşturup alan dolduruyordu ve mysql duruyordu. Bende innodb_buffer_pool_size arttırıp devam ediyorum ta ki bugüne kadar. Bugün o yeri arttırmama rağmen sorun düzelmedi ve mysql hep stop verdi. Bende bazı yanlış şeyler yaptım ve olay iyice karıştı.

Yanlış yaptığım şey şu;

/var/lib/mysql/ibdata1 dosyasını log dosyası sanıp ilk önce pc ye attım sonra sunucudan sildim.
Baktım sorun düzelmedi dosyayı geri attım ama dosya izinleri değişti sanırım. Bu sefer mysql start verdiğimde sürekli şu şekilde log aldım.

160629 17:15:01  InnoDB: Error: page 3627 log sequence number 1122493487
InnoDB: is in the future! Current system log sequence number 328946188.
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.
160629 17:15:01  InnoDB: Error: page 3628 log sequence number 1122310014
InnoDB: is in the future! Current system log sequence number 328946188.
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.
160629 17:15:01  InnoDB: Error: page 3631 log sequence number 1122151212
InnoDB: is in the future! Current system log sequence number 328946188.
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.

Kullandığım panel vestacp. Mysql dosyalarımı alabilsem sunucuyu silip tekrar kuracağım. Ama phpmyadmin den erişemiyorum. Nasıl düzeltebilirim veya sql dosyalarıma ulaşabilirim?

Yardımcı olabilirseniz mutlu olurum.

Aşağıdaki kodlar ile sorunu giderebilirsiniz.

chown -R mysql:mysql /var/lib/mysql/ibdata1
service mysql restart

Malesef hocam birşey değişmedi

Loglar bu şekilde

160629 22:26:07 mysqld_safe Number of processes running now: 0
160629 22:26:07 mysqld_safe mysqld restarted
160629 22:26:07 [Note] /usr/sbin/mysqld (mysqld 5.5.47-0+deb7u1) starting as process 6646 ...
160629 22:26:07 [Note] Plugin 'FEDERATED' is disabled.
160629 22:26:07 InnoDB: The InnoDB memory heap is disabled
160629 22:26:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160629 22:26:07 InnoDB: Compressed tables use zlib 1.2.7
160629 22:26:07 InnoDB: Using Linux native AIO
160629 22:26:07 InnoDB: Initializing buffer pool, size = 5.0M
160629 22:26:07 InnoDB: Completed initialization of buffer pool
160629 22:26:07 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160629 22:26:07 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...
160629 22:26:07 InnoDB: Error: page 7 log sequence number 1116810100
InnoDB: is in the future! Current system log sequence number 328946188.
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/...-recovery.html
InnoDB: for more information.
160629 22:26:07 InnoDB: Error: page 1 log sequence number 329005209
InnoDB: is in the future! Current system log sequence number 328946188.
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/...-recovery.html
InnoDB: for more information.
160629 22:26:07 InnoDB: Error: page 2 log sequence number 727121153
InnoDB: is in the future! Current system log sequence number 328946188.
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/...-recovery.html
InnoDB: for more information.

Sorun çözülmüştür.