Banco MySql não sobe

[teofilob]

Bom dia a todos.

Sou novo aqui no fórum e estou com um Problemão!!!

Eu tenho uma maquina FreeBSD com uma instalação do MySql e estava rodando a algum tempo, a maquina acabou tendo um problema na placa controladora dos discos, que por final tive de trocar, após ter trocado o banco de dados nunca mais subiu.

Ele esta dando a mensagem log com o comando Tail –n 100 aries.dominio.com.br.err

Ao ler as ultimas linhas do arquivo de erro me deparei com esta mensagem

Alguém pode me ajuda?

00...0000
                                                              61,1          60%
080616  9:10:01  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
080616  9:10:01InnoDB: Error: trying to access a stray pointer 0x8ae13ff8
InnoDB: buf pool start is at 0xae04000, end at 0x22e04000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: how to force recovery.
080616  9:10:01InnoDB: Assertion failure in thread 1024 in file ./../include/buf0buf.ic line 259
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
080616  9:10:01 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=0
read_buffer_size=2093056
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 409199 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

080616 09:10:01  mysqld ended
080616  9:10:01  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
080616  9:10:01InnoDB: Error: trying to access a stray pointer 0x8ae13ff8
InnoDB: buf pool start is at 0xae04000, end at 0x22e04000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: how to force recovery.
080616  9:10:01InnoDB: Assertion failure in thread 1024 in file ./../include/buf0buf.ic line 259
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
080616  9:10:01 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=0
read_buffer_size=2093056
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 409199 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

080616 09:10:01  mysqld ended

[Denis Courcy]

Oi, 'teofilob'!

Você mencionou que teve problemas com disco. Isto pode ter crashado algum arquivo do banco conforme informado neste trecho

...It is also possible that this binary or one of the libraries it was linked against is corrupt,...

Tente desinstalar e reinstalar o banco. (Este pode ser o processo menos doloroso).