MySQL Bugs: #24513: Error message o on startup. this is a first time startup.

Bug #24513	Error message o on startup. this is a first time startup.
Submitted:	22 Nov 2006 17:36	Modified:	22 Dec 2006 19:39
Reporter:	lionel geltman	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0	OS:	Windows (windows/xp svc pk 2)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	Startup Failure

Description:
061121 17:56:37  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...
061121 17:56:37  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 43655.
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
InnoDB: Page directory corruption: supremum not pointed to
061121 17:56:37  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 000000000000000000000000000000000000000000000000000000000000000000000; asc                                                                                                                                                                                                            ;InnoDB: End of page dump
061121 17:56:37  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
InnoDB: Page directory corruption: supremum not pointed to
061121 17:56:37  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 00000000000000000000000000000000000000000000000000 many many more ...000000000000000000000000000000000; asc                                                                                                                           ;InnoDB: End of page dump
061121 17:56:37  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
061121 17:56:37 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Got signal 11. Aborting!

061121 17:56:37 [ERROR] Aborting

061121 17:56:37 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

How to repeat:
Try executing the wizard or starting the service.

Thank you for the report.

Are you sure you followed all procedures to recovery your broken tablespace described at http://dev.mysql.com/doc/refman/5.0/en/innodb-backup.html?

If yes, please try using last 5.0.27 version available at dev.mysql.com/downloads/mysql/5.0.html

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".