日志内容中有这些信息： InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 2. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page.是不是数据库文件损坏了？
100316 20:37:27 InnoDB: Page checksum 198097117, prior-to-4.0.14-form checksum 635963325 InnoDB: stored checksum 402310877, prior-to-4.0.14-form stored checksum 635963325 InnoDB: Page lsn 0 113125904, low 4 bytes of lsn at page end 113125904 InnoDB: Page number (if stored to page already) 2, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be an 'inode' page InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 2. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 100316 20:54:31 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: Database page corruption on disk or a failed InnoDB: file read of page 2. InnoDB: You may have to recover from a backup.这次全了不？
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.是不是数据库文件损坏了？
InnoDB: stored checksum 402310877, prior-to-4.0.14-form stored checksum 635963325
InnoDB: Page lsn 0 113125904, low 4 bytes of lsn at page end 113125904
InnoDB: Page number (if stored to page already) 2,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an 'inode' page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100316 20:54:31 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: Database page corruption on disk or a failed
InnoDB: file read of page 2.
InnoDB: You may have to recover from a backup.这次全了不？
InnoDB: than specified in the .cnf file 0 10485760 bytes!
100317 16:55:31 [ERROR] Plugin 'InnoDB' init function returned error.
100317 16:55:31 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
100317 16:55:31 [ERROR] Unknown/unsupported table type: INNODB
100317 16:55:31 [ERROR] Aborting100317 16:55:31 [Warning] Forcing shutdown of 1 plugins
100317 16:55:31 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete
2. 问题出在你的数据库表文件上。