Once you get innodb corruption like this, you generally have to try to dump all your data, shutdown mysql, wipe out all innodb tables and files, then restart mysql & reimport:
It gives the link http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html, to help explain how to start innodb and get your data out. Regards, Gavin Towey -----Original Message----- From: Julien Jabouin [mailto:chatlumo....@gmail.com] Sent: Sunday, October 31, 2010 5:27 AM To: mysql@lists.mysql.com Subject: Innodb can't start Hello, I have a database with tables in innodb and from today database can't be start. I don't know what to do, if your can help, this my mysql log error : Oct 31 13:18:16 myserver mysqld[13681]: 101031 13:18:16 [Note] /usr/sbin/mysqld: Normal shutdown Oct 31 13:18:16 myserver mysqld[13681]: Oct 31 13:18:16 myserver mysqld[13681]: 101031 13:18:16 InnoDB: Starting shutdown... Oct 31 13:18:18 myserver mysqld[13681]: 101031 13:18:18 InnoDB: Shutdown completed; log sequence number 6 2573408134 Oct 31 13:18:18 myserver mysqld[13681]: 101031 13:18:18 [Note] /usr/sbin/mysqld: Shutdown complete Oct 31 13:18:18 myserver mysqld[13681]: Oct 31 13:18:18 myserver mysqld_safe[14191]: ended Oct 31 13:18:19 myserver mysqld_safe[14258]: started Oct 31 13:18:19 myserver mysqld[14261]: 101031 13:18:19 InnoDB: Started; log sequence number 6 2573408134 Oct 31 13:18:19 myserver mysqld[14261]: 101031 13:18:19 [Note] /usr/sbin/mysqld: ready for connections. Oct 31 13:18:19 myserver mysqld[14261]: Version: '5.0.51a-24+lenny3' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian) Oct 31 13:18:20 myserver /etc/mysql/debian-start[14295]: Upgrading MySQL tables if necessary. Oct 31 13:18:20 myserver /etc/mysql/debian-start[14300]: Looking for 'mysql' in: /usr/bin/mysql Oct 31 13:18:20 myserver /etc/mysql/debian-start[14300]: Looking for 'mysqlcheck' in: /usr/bin/mysqlcheck Oct 31 13:18:20 myserver /etc/mysql/debian-start[14300]: This installation of MySQL is already upgraded to 5.0.51a, use --force if you still need to run mysql_upgrade Oct 31 13:18:20 myserver /etc/mysql/debian-start[14307]: Checking for insecure root accounts. Oct 31 13:18:20 myserver /etc/mysql/debian-start[14311]: Triggering myisam-recover for all MyISAM tables Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: Database page corruption on disk or a failed Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: file read of page 178137. Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: You may have to recover from a backup. Oct 31 13:18:22 myserver mysqld[14261]: 101031 13:18:22 InnoDB: Page dump in ascii and hex (16384 bytes): Oct 31 13:18:22 myserver mysqld[14261]: len 16384; hex 4eafb5eb0002b7d9ffffffffffffffff000000061aaac14145bf000000000000000000000000000200ba80050000000000aa0002000200030000000003b0f391000100000000000079fb000000000000c3213332000000000000c3213272010002001b696e66696d756d0004000b000073757072656d756d0010001100168000124367e422b0000000260002655300000019001680001245cdc328ce00001ead0002655400000021ffc680001247f7abe58f00003de20006329000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ... ... ... Oct 31 13:18:22 myserver mysqld[14261]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 Oct 31 13:18:22 myserver mysqld[14261]: 000000000000000000000000007000632e150a1b1aaac141; asc N AE y !32 !2r infimum supremum Cg " & eS E ( eT ! G = 2 Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: Oct 31 13:18:22 myserver mysqld[14261]: p c. A;InnoDB: End of page dump Oct 31 13:18:22 myserver mysqld[14261]: 101031 13:18:22 InnoDB: Page checksum 911668827, prior-to-4.0.14-form checksum 773130779 Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: stored checksum 1320138219, prior-to-4.0.14-form stored checksum 773130779 Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: Page lsn 6 447398209, low 4 bytes of lsn at page end 447398209 Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: Page number (if stored to page already) 178137, Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: Page may be an update undo log page Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: Page may be an index page where index id is 0 31227 Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: (index IDX_ORDER_CREATED_AT of table cosmever/sales_flat_shipment_grid) Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: Database page corruption on disk or a failed Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: file read of page 178137. Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: You may have to recover from a backup. Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: It is also possible that your operating Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: system has corrupted its own file cache Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: and rebooting your computer removes the Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: error. Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: If the corrupt page is an index page Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: you can also try to fix the corruption Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: by dumping, dropping, and reimporting Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: the corrupt table. You can use CHECK Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: TABLE to scan your table for corruption. Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: See also InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: about forcing recovery. Oct 31 13:18:22 myserver mysqld[14261]: InnoDB: Ending processing because of a corrupt database page. Oct 31 13:18:22 myserver mysqld_safe[14322]: Number of processes running now: 0 Oct 31 13:18:22 myserver mysqld_safe[14324]: restarted Oct 31 13:18:22 myserver mysqld[14327]: InnoDB: Log scan progressed past the checkpoint lsn 6 2573408134 Oct 31 13:18:22 myserver mysqld[14327]: 101031 13:18:22 InnoDB: Database was not shut down normally! Oct 31 13:18:22 myserver mysqld[14327]: InnoDB: Starting crash recovery. Oct 31 13:18:22 myserver mysqld[14327]: InnoDB: Reading tablespace information from the .ibd files... Oct 31 13:18:22 myserver mysqld[14327]: InnoDB: Restoring possible half-written data pages from the doublewrite Oct 31 13:18:22 myserver mysqld[14327]: InnoDB: buffer... Oct 31 13:18:22 myserver mysqld[14327]: InnoDB: Doing recovery: scanned up to log sequence number 6 2573408154 Oct 31 13:18:22 myserver mysqld[14327]: 101031 13:18:22 InnoDB: Started; log sequence number 6 2573408154 Oct 31 13:18:22 myserver mysqld[14327]: 101031 13:18:22 [Note] /usr/sbin/mysqld: ready for connections. Oct 31 13:18:22 myserver mysqld[14327]: Version: '5.0.51a-24+lenny3' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian) Thanks if you have an idea... -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=gto...@ffn.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you are notified that reviewing, disseminating, disclosing, copying or distributing this e-mail is strictly prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any loss or damage caused by viruses or errors or omissions in the contents of this message, which arise as a result of e-mail transmission. [FriendFinder Networks, Inc., 220 Humboldt Court, Sunnyvale, CA 94089, USA, FriendFinder.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
