视频1 视频21 视频41 视频61 视频文章1 视频文章21 视频文章41 视频文章61 推荐1 推荐3 推荐5 推荐7 推荐9 推荐11 推荐13 推荐15 推荐17 推荐19 推荐21 推荐23 推荐25 推荐27 推荐29 推荐31 推荐33 推荐35 推荐37 推荐39 推荐41 推荐43 推荐45 推荐47 推荐49 关键词1 关键词101 关键词201 关键词301 关键词401 关键词501 关键词601 关键词701 关键词801 关键词901 关键词1001 关键词1101 关键词1201 关键词1301 关键词1401 关键词1501 关键词1601 关键词1701 关键词1801 关键词1901 视频扩展1 视频扩展6 视频扩展11 视频扩展16 文章1 文章201 文章401 文章601 文章801 文章1001 资讯1 资讯501 资讯1001 资讯1501 标签1 标签501 标签1001 关键词1 关键词501 关键词1001 关键词1501 专题2001
服务器断电后mysql无法启动
2020-11-09 16:38:50 责编:小采
文档


无法启动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/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  65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88  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 24559638InnoDB: Page lsn 2 1554755772, low 4 bytes of lsn at page end 15508857InnoDB: 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

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

下载本文
显示全文
专题