#1030 - Got error 176 "Read page with wrong checksum" from storage engine Aria

MysqlPhpmyadminMariadb

Mysql Problem Overview


Created a new database but can't create new user account due to this error. Does anyone know how to fix this? I can't find any solution to fix this.

> 1030 - Got error 176 "Read page with wrong checksum" from storage engine Aria

error picture

Mysql Solutions


Solution 1 - Mysql

In my case above solution not worked. But the solution is similar to suggest by the @user13439511

Follow the below steps.

  1. Select "mysql" database from the list of database. enter image description here

  2. Select all tables inside "mysql" database. enter image description here

  3. Scroll down and select "Repair Table" option in combobox.

  4. Click on Go button.

Done.

Solution 2 - Mysql

I was attempting to add a user to a new database with 'Privileges' and received this error: "#1030 - Got error 176 "Read page with wrong checksum" from storage engine Aria"

Select mysql from the list of databases. From the Table list, tick the box beside 'db'. Scroll to the bottom of the page, in the selection box that says 'With selected' scroll down to and select 'Repair Table' then select 'Go'. Worked for me .:m

Solution 3 - Mysql

In the PHPMyAdmin panel go to the MySQL database, select the DB table and from the bottom dropdown menu select the repair table option.Your error will be resolved.

Solution 4 - Mysql

Spent a long time trying to fix this, but the repair method wasn't working. MySQL repairs thinks it fixed all the tables, but it wasn't fixing the error (checking the tables showed they still had errors).

I did fix it by dropping and recreating the affected tables. Instructions as follows:

  1. Select the 'mysql' database
  2. Select all the tables as described in other fixes, but run a 'check tables' instead of a 'repair tables'.
  3. For tables that are broken, (mine was the mysql.db table), you need to select the table and export it. In phpmyadmin, view the table and click export.
  4. Select custom export, and check the 'Add DROP TABLE / TRIGGER statement' option, then export. Save the sql file.
  5. In the import tab, import the sql file you just created.

This drops the table and recreates it, which fixed the issues I was having.

I'm not sure why this worked, where as repairing the table didn't.

Solution 5 - Mysql

In my phpMyAdmin version (5.0.4) the mysql db gets corrupted when stop and restart the MySQL server, I solved it by running the task as a service

Solution 6 - Mysql

If you can't access to the structure of mysql database, just log out then try again to repaire tables of it.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionnephView Question on Stackoverflow
Solution 1 - MysqlPankaj LahotiView Answer on Stackoverflow
Solution 2 - Mysqluser13439511View Answer on Stackoverflow
Solution 3 - MysqlSalman TayyabView Answer on Stackoverflow
Solution 4 - MysqlSnowblindView Answer on Stackoverflow
Solution 5 - MysqlIsmael rojasView Answer on Stackoverflow
Solution 6 - MysqlHesam MoosapourView Answer on Stackoverflow