mysql data文件夹恢复 错误_mysql崩溃！数据恢复不了！，在线等！

mysql崩溃！数据恢复不了！，在线等！

舞墨落凡尘

2020-06-03 16:24:35

MYSQL一直运行得好好的，但10号突然就死了。然后我尝试重启，但怎么也起不来了。只能重装MYSQL！重装后，想用二进制日志文件恢复。共有三个二进制日志文件，前2个很正常，但是第三个就报错：“ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 509607, event_type: 2” ！尝试用二进制日志文件恢复失败！然后我把之前的MYSQL下的DATA文件夹覆盖到新的DATA文件夹下，开始不能启动MYSQL。查了一些资料后可以启动了，但是进数据库后仍然报错：“Incorrect information in file: './naihaibank/bbs_api.frm' ” ！ 查了很多方法都没用！不知道是不是文件损坏了！服务器环境是：redhat 5.5 mysql 5.0.67 。贴出部分MYSQL错误日志：Number of processes running now: 0101110 11:07:27 mysqld restartedInnoDB: Log scan progressed past the checkpoint lsn 0 409875142101110 11:07:27 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...InnoDB: Doing recovery: scanned up to log sequence number 0 409875152InnoDB: Error: tried to read 16384 bytes at offset 0 109232128.InnoDB: Was only able to read 4096.InnoDB: Fatal error: cannot read from file. OS error number 17.101110 11:07:40InnoDB: Assertion failure in thread 3086730944 in file os0file.c line 2211InnoDB: We intentionally generate a memory trap.InnoDB: Submit a detailed bug report to InnoDB: If you get repeated assertion failures or crashes, evenInnoDB: immediately after the mysqld startup, there may beInnoDB: corruption in the InnoDB tablespace. Please refer toInnoDB: InnoDB: about forcing recovery.101110 11:07:40 - mysqld got signal 11 ;This could be because you hit a bug. It is also possible that this binaryor one of the libraries it was linked against is corrupt, improperly built,or misconfigured. This error can also be caused by malfunctioning hardware.We will try our best to scrape up some info that will hopefully help diagnosethe problem, but since we have already crashed, something is definitely wrongand this may fail.

分享到