- 论坛徽章:
- 0
|
数据库硬盘坏了 把data文件夹 拷了出来，把新搭的数据库 下面的data文件 替换了下 mysql就启动不了
看了下err 文档 实在看不懂 求大神帮帮忙 主要数据十分重要 谢谢了
161015 14:32:44 [Note] Plugin 'FEDERATED' is disabled.
161015 14:32:44 InnoDB: The InnoDB memory heap is disabled
161015 14:32:44 InnoDB: Mutexes and rw_locks use Windows interlocked functions
161015 14:32:44 InnoDB: Compressed tables use zlib 1.2.3
161015 14:32:44 InnoDB: Initializing buffer pool, size = 1.0G
161015 14:32:44 InnoDB: Completed initialization of buffer pool
161015 14:32:44 InnoDB: highest supported file format is Barracuda.
InnoDB: ##########################################################
InnoDB: WARNING!
InnoDB: The log sequence number in ibdata files is higher
InnoDB: than the log sequence number in the ib_logfiles! Are you sure
InnoDB: you are using the right ib_logfiles to start up the database?
InnoDB: Log sequence number in ib_logfiles is 4212811571, log
InnoDB: sequence numbers stamped to ibdata file headers are between
InnoDB: 5398286317 and 5398286317.
InnoDB: ##########################################################
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
161015 14:32:44 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...
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 230.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 414.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 318.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 54.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 7166.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 534.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 726.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 390.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
161015 14:32:51 InnoDB: Error: page 2 log sequence number 6448130721
InnoDB: is in the future! Current system log sequence number 4212811571.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
InnoDB: for more information.
161015 14:32:51 InnoDB: Error: page 4 log sequence number 6371107030
InnoDB: is in the future! Current system log sequence number 4212811571.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
InnoDB: for more information.
161015 14:32:51 InnoDB: Error: page 5 log sequence number 6448279778
InnoDB: is in the future! Current system log sequence number 4212811571.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB:
InnoDB: for more information.
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 6.
InnoDB: You may have to recover from a backup.
161015 14:32:51 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 244d3408000000060000000000000
（后面就是n个0和F）
InnoDB: End of page dump
161015 14:32:52 InnoDB: Page checksum 609039368, prior-to-4.0.14-form checksum 3999017343
InnoDB: stored checksum 609039368, prior-to-4.0.14-form stored checksum 793934317
InnoDB: Page lsn 1 2153304077, low 4 bytes of lsn at page end 4212603187
InnoDB: Page number (if stored to page already) 6,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 6.
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
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
161015 14:32:52 InnoDB: Assertion failure in thread 5116 in file buf0buf.c line 3608
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB:
InnoDB: about forcing recovery.
|
|
免费注册
发表于 2016-10-15 14:33
