Проблема с запуском БД после краша. Видео сервер на Ubuntu. Стоит приложение zoneminder с приуроченной БД Maria db. После отключения света, выдаёт такой лог. 230309 13:13:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 230309 13:13:18 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 189 ... 230309 13:13:18 InnoDB: The InnoDB memory heap is disabled 230309 13:13:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins 230309 13:13:18 InnoDB: Compressed tables use zlib 1.2.7 230309 13:13:18 InnoDB: Using Linux native AIO 230309 13:13:18 InnoDB: Initializing buffer pool, size = 128.0M 230309 13:13:18 InnoDB: Completed initialization of buffer pool 230309 13:13:18 InnoDB: highest supported file format is Barracuda. 230309 13:13:18 InnoDB: Starting crash recovery from checkpoint LSN=825923095435 InnoDB: Restoring possible half-written data pages from the doublewrite buffer... InnoDB: Error: trying to access page number [Телефон скрыт] in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 230309 13:13:18 InnoDB: Assertion failure in thread 140222436034688 in file fil0fil.c line 5496 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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. 230309 13:13:18 [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 http://kb.askmonty.org/en/reporting-bugs 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: 5.5.68-MariaDB key_buffer_size=[Телефон скрыт] read_buffer_size=131072 max_used_connections=0 max_threads=153 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466719 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 0x48000 /usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x5580aa630cad] /usr/libexec/mysqld(handle_fatal_signal+0x515)[0x5580aa244975] sigaction.c:0(__restore_rt)[0x7f88143bc630] :0(__GI_raise)[0x7f8812ae3387] :0(__GI_abort)[0x7f8812ae4a78] /usr/libexec/mysqld(+0x6ca9ad)[0x5580aa46b9ad] /usr/libexec/mysqld(+0x6973d3)[0x5580aa4383d3] /usr/libexec/mysqld(+0x680567)[0x5580aa421567] /usr/libexec/mysqld(+0x644d3d)[0x5580aa3e5d3d] /usr/libexec/mysqld(+0x645a1c)[0x5580aa3e6a1c] /usr/libexec/mysqld(+0x64817e)[0x5580aa3e917e] /usr/libexec/mysqld(+0x631495)[0x5580aa3d2495] /usr/libexec/mysqld(+0x5e8344)[0x5580aa389344] /usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x5580aa2469f8] /usr/libexec/mysqld(+0x37c4c6)[0x5580aa11d4c6] /usr/libexec/mysqld(_Z11plugin_initPiPPci+0x559)[0x5580aa1229e9] /usr/libexec/mysqld(+0x2ed02a)[0x5580aa08e02a] /usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x5c2)[0x5580aa0911c2] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f8812acf555] /usr/libexec/mysqld(+0x2e71cd)[0x5580aa0881cd] 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. 230309 13:13:18 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended.