MariaDB ,problemas con InnoDB , ibdata1 corrupto

3 envíos / 0 nuevos
Último envío
#1 Sáb, 09/12/2017 - 17:26
Imagen de EtHome
se unió: 09/04/16

MariaDB ,problemas con InnoDB , ibdata1 corrupto


Buenas, tengo un problema con MariaDB, la base de datos viene de mysql 5.5. y lo upgrade a Mariadb, funciono perfecto por un tiempo pero de repente un dia no arranco mas.
El problema consiste en que el servicio no inicia ya que detecta que el workspace esta corrupto.
Alguien sabe como repararlo?

cat /var/log/mysql/error.log
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-12-09 16:48:48 140010911072832 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: The InnoDB memory heap is disabled
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: Using Linux native AIO
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: Using SSE crc32 instructions
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: Completed initialization of buffer pool
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: Highest supported file format is Barracuda.
2017-12-09 16:48:48 140010911072832 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace ./ibdata1 page  [page id: space=0, page number=481]. You may have to recover from a backup.
2017-12-09 16:48:48 7f56d49e8240 InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex c9377fda000001e10000000000000000000000042c118826000200000000000000000000000000010110011cffffffff0000ffffffff0000000200560000000000000143147200000001000001e1002c000001e1002c000000000664c7ec00000000000000000001011000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000011c0b006804803221ea01101036011068048031e828011c01340b026704004b55b9012801400b0368048031e8290134000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
InnoDB: End of page dump
2017-12-09 16:48:48 7f56d49e8240 InnoDB: uncompressed page, stored checksum in field1 3375857626, calculated checksums for field1: crc32 454293285, innodb 564149632, none 3735928559, stored checksum in field2 3001088818, calculated checksums for field2: crc32 454293285, innodb 2703796530, none 3735928559, page LSN 4 739346470, low 4 bytes of LSN at page end 739346470, page number (if stored to page already) 481, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: page type 2 meaning UNDO LOG
InnoDB: Page may be an insert undo log page
2017-12-09 16:48:48 140010911072832 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to for information about forcing recovery.
2017-12-09 16:48:48 140010911072832 [ERROR] InnoDB: Ending processing because of a corrupt database page.
2017-12-09 16:48:48 7f56d49e8240  InnoDB: Assertion failure in thread 140010911072832 in file line 21960
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.
171209 16:48:48 [ERROR] mysqld got signal 6 ;
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.

To report this bug, see

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.

Server version: 10.1.26-MariaDB-0+deb9u1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352445 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
stack_bottom = 0x0 thread_stack 0x30000
The manual page at contains
information that should help you find out what is causing the crash.


Sáb, 09/12/2017 - 22:26
Imagen de rockyiii
se unió: 11/01/16

seria bueno saber si mariadb se esta ejecutando

systemctl status mariadb

si solo es que la base de datos tiene algun problema, fijate si alguno de estos comandos te ayuda

mysqlcheck --optimize nombre_base_datos --user="root" --passwor