u010917843
汝不见
2015-05-20 04:46

服务器断电后mysql无法启动

  • 断电
  • mysql
  • 无法启动

因意外导致服务器断电,重启后发现mysql起不来了

 [root@cacti ~]# service mysqld restart
停止 mysqld:                                              [确定]
MySQL Daemon failed to start.
正在启动 mysqld:                                          [失败]

查看日志:

 [root@cacti ~]# tail -100 /var/log/mysqld.log 
 150520 12:21:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150520 12:21:12  InnoDB: Initializing buffer pool, size = 8.0M
150520 12:21:12  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 2 1552263436
150520 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 doublewrite
InnoDB: 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 failed
InnoDB: 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 dump
150520 12:21:12  InnoDB: Page checksum 3392922109, prior-to-4.0.14-form checksum 1831220034
InnoDB: stored checksum 3427825255, prior-to-4.0.14-form stored checksum 2455963898
InnoDB: Page lsn 2 1554755772, low 4 bytes of lsn at page end 1556408857
InnoDB: Page number (if stored to page already) 206,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 206.
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-innodb-recovery.html
InnoDB: 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

mysql新手一个,希望大家能帮帮忙分析下,谢谢!

  • 点赞
  • 回答
  • 收藏
  • 复制链接分享

5条回答