Mysql error "#1030 - Got error -1 from storage engine" when doing insert/update queries

I am starting to learn manipulating some long list of data from datalogs in mysql, around 300k entries, and it is being added by about 1k off entries everyday, it was working fine in a week then suddently I'm not able to write in the db. Here are the errors that I'm getting:

-
I can do select queries but when I do insert and update I am
getting this error:


#1030 - Got error -1 from storage engine

-
When I try to change the engine type from InnoDB to MyISAM, I'm
getting this error:


#1025 - Error on rename of './dbname/tablename'
to './dbname/#sql2-500-37' (errno: -1

-
I can create new tables

These are the things that I have checked:

-
Any of my disk space is still more than 50%, I have checked it using df

-
Last line in the MySQL error log (/var/log/mysql/error.log):

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.

-
Tried restarting server & mysql service

-
I also tried doubling the values in the MySQL config file but it seems it doesn't help, here is my config file (/etc/mysql/my.cnf)

```
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0

[mysqld]
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking

bind-address = 127.0.0.1
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8

myisam-recover = BACKUP
#max_connections = 100
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M

expire_lo

You will notice in the errors this message


InnoDB: innodb_force_recovery is on: we do not allow InnoDB: database
modifications by the user. Shut down

So please remove the innodb_force_recovery option from my.cnf

StackExchange Database Administrators Q#111529, answer score: 5