MySQL not starting
2022-05-06 16:25:11 0x7f728d7fa700 InnoDB: Assertion failure in file /builddir/build/BUILD/mariadb-10.3.34/storage/innobase/btr/btr0cur.cc line 313
InnoDB: Failing assertion: btr_page_get_next(latch_leaves.blocks[0]->frame) == page_get_page_no(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to InnoDB Recovery Modes
InnoDB: about forcing recovery.
220506 16:25:11 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
To report this bug, see
-
Is MySQL up and running at the time you tried that dump? 0 -
Is MySQL up and running at the time you tried that dump?
Yes running in Mode 4 Recovery,Dump created up to 4GB then it got stopped I had moved that database data directory out of /var/lib/mysql and run the dump again it goes fine0 -
So you were able to do the dump after moving the files? 0 -
So you were able to do the dump after moving the files?
Yes but the same thing happen after dumping of 16GB and then it got stopped due to this i need to start it again from first after moving the file Is there anyway easier ?0 -
cPanel isn't able to provide assistance with InnoDB corruption, as that often needs to be handled by MySQL administrators that are familiar with fixing those issues. If not, you run the risk of data loss. If the steps in that guide I provided aren't working well, it's likely time to call in some outside help. 0 -
Try your mysqldump with -f. That should "force" it to continue even if there are errors. You're obviously going to be missing things, but better than having do the mysqldump over and over. 0
Please sign in to leave a comment.
Comments
8 comments