Record the failure to start mysql after power failure

Record the helpless power failure caused by a failure to start mysql after a power failure. Mysql cannot be started. 1. view error 130313 15:31:13 [Note] Plugin 'federated 'is disabled. 130313 15:31:13 InnoDB: Initializing buffer pool, size = 107.0 M 130313 15:31:13 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 2 3605230851 130313 15:31:13 InnoDB: database was not shut down normally! InnoDB: Starting crash recovery. innoDB: Reading tablespace information from. ibd files... innoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... innoDB: Doing recovery: scanned up to log sequence number 2 3605259847 130313 15:31:14 InnoDB: Starting an apply batch of log records to the database... innoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 19 20 21 22 23 24 26 26 28 29 30 31 32 33 34 35 36 38 39 40 41 42 43 44 45 46 48 49 50 51 53 54 55 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: apply batch completed 130313 15:31:14 InnoDB: Started; log sequence number 2 3605259847 130313 15:31:14 [Note] Event Scheduler: Loaded 0 events 130313 15:31:14 [Note] D: \ Program Files (x86) \ MySQL Server 5.1 \ bin \ mysqld: ready for connections. version: '5. 1.63-community 'socket: ''port: 3306 MySQL Community Server (GPL) 130313 15:31:16 InnoDB: Assertion failure in thread 5732 in file. \ fsp \ fsp0fsp. c line 3341 InnoDB: We intentionally generate a memory trap. innoDB: Submit a detailed bug report http://bugs.mysql.com . InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: Snapshot uption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. Some solutions have been found online. Bit to solve the problem. Finally, [mysqld] innodb_force_recovery = 4 a. After the instance is forcibly started, the database data can only be viewed but cannot be modified or inserted. B. Run the mysqldump command to export the data. C. Recreate the database, and d. import data. Indirectly solved the problem.