Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add FAQ MariaDB fix corrupted database after blackout #422

Open
MichaelOv opened this issue Feb 27, 2024 · 0 comments
Open

Add FAQ MariaDB fix corrupted database after blackout #422

MichaelOv opened this issue Feb 27, 2024 · 0 comments
Labels

Comments

@MichaelOv
Copy link
Member

Possible errors:

-Upgrade after a crash is not supported.
-Generic error
-Database corrupt
-Failed to start MariaDB

Solution:

This error also happens when your Database data is corrupt. You may fix this issue by moving your Db data files (ib_logfile0 and ib_logfile1) mentioned below to another location. ib_logfile0 and ib_logfile1 are system tablespace for the InnoDB infrastructure. These files contains several classes for information vital for InnoDB. You may read about these files here.

Before following below steps please keep a copy of files (ib_logfile0 and ib_logfile1) so you may restore your data in case it is lost:

Follow below steps:

Login to server via SSH with root access.
Navigate to /var/lib/mysql.
If you see files like, ib_logfile0 and ib_logfile1, rename or move them to some other folder.
Stop and start the MySQL service by running sudo service mysql stop and sudo service mysql start

And then

Systemctl status mariadb.service

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant