mysql+挂了不能启动不了了,MySQL启动失败,磁盘挂载不正确导致的主库启动不起来怎么解决?...

这篇博客讲述了由于磁盘挂载错误导致MySQL主库无法启动的问题,具体表现为日志恢复过程中出现错误,系统找不到指定路径。解决方案包括检查分区UUID、确认挂载文件是否正确及重新挂载分区并更新fstab文件。在修复后,数据库成功启动,但出现了权限表不存在的错误。这提示可能还需要进一步修复MySQL的权限配置。
摘要由CSDN通过智能技术生成

磁盘挂载不正确导致的主库启动不起来:

Recovery process statistics

Checked pages by doublewrite buffer: 128

Overwritten pages from doublewrite: 0

Recovered pages by io_thread: 143

Recovered pages by main thread: 0

Parsed log records to apply: 139463

Sum of the length: 964413

Applied log records: 135257

Sum of the length: 940059

Pages which are already new enough: 128 (It may not be accurate, if turns > 1)

Oldest page's LSN: 39274

Newest page's LSN: 1597908

============================================================

171205 10:04:01 InnoDB: Operating system error number 2 in a file operation.

InnoDB: The error means the system cannot find the path specified.

InnoDB: cannot open ib_lru_dump

171205 10:04:01 InnoDB: Waiting for the background threads to start

171205 10:04:02 Percona XtraDB (https://www.percona.com) 1.1.8-rel24.1 started; log sequence number 1597915

171205 10:04:02 [Note] Recovering after a crash using /home/mysql/binlog

171205 10:04:02 [Note] Starting crash recovery...

171205 10:04:02 [Note] Crash recovery finished.

171205 10:04:02 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist

171205 10:04:02 mysqld_safe mysqld from pid file /home/mysql/mysql.pid ended

解决: 1、查看分区UUID blkid 2、查看/etc/fstatb文件挂盘文件是否正确 3、重新挂载分区,写入fstab文件

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值