Article ID: 126863, created on Sep 11, 2015, last review on Sep 20, 2015

  • Applies to:
  • Plesk 12.0 for Linux


Unable to restore/insert into MySQL database, the following error occurs:

ERROR 1030 (HY000): Got error -1 from storage engine

Mysql log /var/log/mysql.log contains following records:

ERROR 1030 (HY000): Got error -1 from storage engine
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.

Server has enough free disk space and RAM memory.


MySQL is running with innodb_force_recovery mode.


  1. Check /etc/my.cnf and make sure innodb_force_recovery is not set:

    # grep 'force_recovery' /etc/my.cnf
    innodb_force_recovery = 5
  2. If it is enabled, switch innodb_force_recovery off by changing the value to '0':

    # grep 'force_recovery' /etc/my.cnf
    innodb_force_recovery = 0
  3. Restart mysql:

    # /etc/init.d/mysqld restart

Please refer to the following mysql guide for more details:

"Only set innodb_force_recovery to a value greater than 0 in an emergency situation, so that you can start InnoDB and dump your tables. Before doing so, ensure that you have a backup copy of your database in case you need to recreate it. Values of 4 or greater can permanently corrupt data files....innodb_force_recovery is 0 by default (normal startup without forced recovery)."

Plesk do not make changes into /etc/my.cnf by setting innodb_force_recovery to enabled state.

Search Words

ERROR 1030 (HY000): Got error -1 from storage engine


Unable to restore/insert into database

29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7

Email subscription for changes to this article
Save as PDF