【已完成】极速安装mssql后，mysql就无法启动了
本帖最后由 堡塔运维香菜卷 于 2023-3-30 16:10 编辑面板版本：7.8.0
浏览器版本：火狐
什么设备：云服务器
什么系统和架构：
Windows-2012R2-Datacenter-cn问题具体描述：宝塔面板操作安装mssql环境，极速安装，提示我只能面板下载完成后需要远程服务器安装mssql数据库。待下载完毕后，mysql就无法启动，找不到原因，提示超时启动
重现方式：宝塔面板后台启动失败以及远程服务器里面的服务也启动失败
附件截图：就是超时启动失败
您好，这边不是很能理解您说的，您现在是mysql无法启动是吗？截图上传一下您mysql的日志看看报错原因。https://www.bt.cn/bbs/data/attachment/forum/202302/09/173248qcxxpl1axy7yycxf.png
2023-03-29 18:06:43 5156 InnoDB: Completed initialization of buffer pool
2023-03-29 18:06:43 5156 InnoDB: Highest supported file format is Barracuda.
2023-03-29 18:06:43 5156 InnoDB: The log sequence numbers 1625977 and 1625977 in ibdata files do not match the log sequence number 1626134 in the ib_logfiles!
2023-03-29 18:06:43 5156 InnoDB: Database was not shutdown normally!
2023-03-29 18:06:43 5156 InnoDB: Starting crash recovery.
2023-03-29 18:06:43 5156 InnoDB: Reading tablespace information from the .ibd files...
2023-03-29 18:06:43 5156 InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lakala_pos_com/wp_actionscheduler_actions uses space ID: 6 at filepath: .\lakala_pos_com\wp_actionscheduler_actions.ibd. Cannot open tablespace lakala_pos_com_backup/wp_actionscheduler_actions which uses space ID: 6 at filepath: .\lakala_pos_com_backup\wp_actionscheduler_actions.ibd
InnoDB: Error: could not open single-table tablespace file .\lakala_pos_com_backup\wp_actionscheduler_actions.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here. 您好，联系数据恢复机构处理，您这个数据表存在损坏状态。导致MySQL无法正常启动 本来是正常的，就是因为在面板操作安装mssql数据库，长时间没动导致mysql坏掉，希望优化这方面
页:
[1]