mysqld start error

[Gloups]

Hi all, this may be a newbie style question but i'm actually blocked with that problem.

I had a look to mysql bug tracker and in the doc but i didn't found my solution.

during the start of mysqld i've got those messages:

080630 14:55:16 mysqld started
080630 14:55:16 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: Error: tried to read 1048576 bytes at offset 0 1048576.
InnoDB: Was only able to read 925696.
InnoDB: Fatal error: cannot read from file. OS error number 17.
080630 14:55:17InnoDB: Assertion failure in thread 3086911744 in file os0file.c line 2176
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/mysql/en/Forcing_recovery.html

InnoDB: about forcing recovery.
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=131072
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 = 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbf96f1a8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8174693
0xdae420
0xb4844000
0x8396681
0x83bbce3
0x831a807
Stack trace seems successful - bottom reached
Please read

http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html

and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at

http://www.mysql.com/doc/en/Crashing.html

contains
information that should help you find out what is causing the crash.
080630 14:55:18 mysqld ended




I also used resolve_stack_dump as documented and i got those messages:


0x8174693 handle_segfault + 643
0xdae420 (?)
0xb4844000 _end + -1407626232
0x8396681 trx_sys_doublewrite_init_or_restore_pages + 385
0x83bbce3 recv_recovery_from_checkpoint_start + 5091
0x831a807 innobase_start_or_create_for_mysql + 5703



Actually i realy dont know what to do.


Thank's in advance for any help

 

[TonyGroves]

It looks more like a filesystem problem. Have you done a fsck on it?

 

[Gloups]

Yes i've just tried that but it's clean