MySQL Server has corrupted data on my Raspberry Pi

[Rainer Merzenich]

Hi,

I'm using a MySQL database server on my Raspberry Pi for storing a lot of data, but now the database is broken (the SD card is pretty old so I guess that there is an I/O error). In order to come to a solution I pulled the data out of the Pi and into a VM with the exact same MySQL version. Everything starts and I can work with the DB but when I access a certain table the database server crashes. Also running "CHECK TABLE" the database server crashes. I even tried "innodb_force_recovery" without success.

What should I do to recover my data?

Regards!

The MySQL error file looks like:

160406 14:42:16 [Note] Plugin 'FEDERATED' is disabled.
160406 14:42:16 InnoDB: The InnoDB memory heap is disabled
160406 14:42:16 InnoDB: Mutexes and rw_locks use Windows interlocked functions
160406 14:42:16 InnoDB: Compressed tables use zlib 1.2.3
160406 14:42:16 InnoDB: Initializing buffer pool, size = 18.0M
160406 14:42:16 InnoDB: Completed initialization of buffer pool
160406 14:42:16 InnoDB: highest supported file format is Barracuda.
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
160406 14:42:16  InnoDB: Waiting for the background threads to start
160406 14:42:17 InnoDB: 5.5.44 started; log sequence number 0
160406 14:42:17 InnoDB: !!! innodb_force_recovery is set to 6 !!!
160406 14:42:17 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
160406 14:42:17 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
160406 14:42:17 [Note] Server socket created on IP: '0.0.0.0'.
160406 14:42:17 [Note] Event Scheduler: Loaded 0 events
160406 14:42:17 [Note] mysqld: ready for connections.
Version: '5.5.44'  socket: ''  port: 3306  MySQL Community Server (GPL)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2449.
InnoDB: You may have to recover from a backup.
160406 14:42:20  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 

... omitted ...

InnoDB: End of page dump
160406 14:42:20  InnoDB: Page checksum 3973849222, prior-to-4.0.14-form checksum 2439485980
InnoDB: stored checksum 3707364764, prior-to-4.0.14-form stored checksum 2439485980
InnoDB: Page lsn 0 332231599, low 4 bytes of lsn at page end 332231599
InnoDB: Page number (if stored to page already) 2449,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 67108864
InnoDB: Page may be an index page where index id is 53
InnoDB: (index "PRIMARY" of table "tv-guide"."item")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2449.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2467.
InnoDB: You may have to recover from a backup.
160406 14:42:20  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 

... omitted ...

InnoDB: End of page dump
160406 14:42:20  InnoDB: Page checksum 2716226139, prior-to-4.0.14-form checksum 3520442017
InnoDB: stored checksum 1360108016, prior-to-4.0.14-form stored checksum 3520442017
InnoDB: Page lsn 0 332878432, low 4 bytes of lsn at page end 332878432
InnoDB: Page number (if stored to page already) 2467,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an index page where index id is 53
InnoDB: (index "PRIMARY" of table "tv-guide"."item")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2467.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
160406 14:42:20  InnoDB: Assertion failure in thread 3764 in file rem0rec.c line 569
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
12:42:20 UTC - mysqld got exception 0x80000003 ;
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.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

key_buffer_size=11534336
read_buffer_size=65536
max_used_connections=1
max_threads=100
thread_count=1
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 44000 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x21f3e70
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
5bece0    mysqld.exe!my_thread_name()
7193ae    mysqld.exe!my_mb_ctype_mb()
665485    mysqld.exe!my_osmaperr()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2295de8): SELECT * FROM item WHERE day = 200Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.