Mysql cannot be started after the server is powered off

An unexpected server power failure occurs. after the server is restarted, mysql cannot be started. & quot; [root @ cacti ~] # Servicemysqldrestart stop mysqld: [OK] MySQLDaemonfailedtostart. starting mysqld: [failed] & quot; View Log: & quot; [root @ cacti ~] # Tail-100varlogmysqld.log15052012: 21: 12mysqld_safeStartingmysqlddaemonwit... unable to start mysql power-off

An unexpected server power failure occurs. after the server is restarted, mysql cannot be started.

[Root @ cacti ~] # Service mysqld restart stop mysqld: [OK] MySQL Daemon failed to start. starting mysqld: [failed]

View logs:

 [root@cacti ~]# tail -100 /var/log/mysqld.log  150520 12:21:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql150520 12:21:12  InnoDB: Initializing buffer pool, size = 8.0M150520 12:21:12  InnoDB: Completed initialization of buffer poolInnoDB: Log scan progressed past the checkpoint lsn 2 1552263436150520 12:21:12  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 doublewriteInnoDB: buffer...150520 12:21:12  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 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 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: Database page corruption on disk or a failedInnoDB: file read of page 206.InnoDB: You may have to recover from a backup.150520 12:21:12  InnoDB: Page dump in ascii and hex (16384 bytes):len 16384; hex cc507667000000ce0000000000000000000000025cabb0bc000200000000000000000000000000021e751eb0ffffffff0000ffffffff000000021dbb0000000000000002123200000001000000ce002c000000ce002c000000000304a196000000000304a1970001011000000000000000000000014...................oDB: End of page dump150520 12:21:12  InnoDB: Page checksum 3392922109, prior-to-4.0.14-form checksum 1831220034InnoDB: stored checksum 3427825255, prior-to-4.0.14-form stored checksum 2455963898InnoDB: Page lsn 2 1554755772, low 4 bytes of lsn at page end 1556408857InnoDB: Page number (if stored to page already) 206,InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0InnoDB: Page may be an update undo log pageInnoDB: Database page corruption on disk or a failedInnoDB: file read of page 206.InnoDB: You may have to recover from a backup.InnoDB: It is also possible that your operatingInnoDB: system has corrupted its own file cacheInnoDB: and rebooting your computer removes theInnoDB: error.InnoDB: If the corrupt page is an index pageInnoDB: you can also try to fix the corruptionInnoDB: by dumping, dropping, and reimportingInnoDB: the corrupt table. You can use CHECKInnoDB: TABLE to scan your table for corruption.InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.htmlInnoDB: about forcing recovery.InnoDB: Ending processing because of a corrupt database page.150520 12:21:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

I am a beginner in mysql. I hope you can help me with the analysis. thank you!