Cara Mengambil Data dari MySQL yg tidak bisa Start

89 views
Skip to first unread message

Much. Yusron Arif

unread,
Jan 11, 2018, 4:47:29 AM1/11/18
to MySQL Indonesia
Agan-agan mohon bantuannya, 
gimana cara nya untuk nyelamatin data yg ada di mysql, kondisi mysql servernya selalu "force stop" ketika di "start"?
table engine nya pake InnoDB

pesan error nya spt ini:

180111 14:39:01  InnoDB: Error: page 49153 log sequence number 6 1093227438
InnoDB: is in the future! Current system log sequence number 0 44233.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: for more information.
180111  ...
InnoDB: ...
InnoDB: ...
InnoDB: ...
InnoDB: ...
InnoDB: ...
180111 14:39:01  InnoDB: Error: page 83510 log sequence number 0 10794773
InnoDB: is in the future! Current system log sequence number 0 44564.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: for more information.
180111 14:39:01  InnoDB: Assertion failure in thread 800 in file .\fsp\fsp0fsp.c line 3256
InnoDB: Failing assertion: xdes_get_bit(descr, XDES_FREE_BIT, buf_frame_get_page_no(header) % FSP_EXTENT_SIZE, mtr) == FALSE
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: about forcing recovery.
InnoDB: Thread 6320 stopped in file .\os\os0sync.c line 574
InnoDB: Thread 9944 stopped in file .\os\os0sync.c line 271


Reply all
Reply to author
Forward
0 new messages