And this is the result of the error.log
root@DietPi:~# cat /var/log/mysql/error.log
2021-02-23 14:51:09 0 [Note] InnoDB: Using Linux native AIO
2021-02-23 14:51:09 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-02-23 14:51:09 0 [Note] InnoDB: Uses event mutexes
2021-02-23 14:51:09 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-02-23 14:51:09 0 [Note] InnoDB: Number of pools: 1
2021-02-23 14:51:09 0 [Note] InnoDB: Using generic crc32 instructions
2021-02-23 14:51:09 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-02-23 14:51:09 0 [Note] InnoDB: Completed initialization of buffer pool
2021-02-23 14:51:09 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-02-23 14:51:09 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=265033300
2021-02-23 14:51:09 0 [Note] InnoDB: Starting final batch to recover 1 pages from redo log.
2021-02-23 14:51:09 0x5784f3e0 InnoDB: Assertion failure in file /build/mariadb-10.3-S9bYSW/mariadb-10.3-10.3.27/storage/innobase/rem/rem0rec.cc line 815
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
210223 14:51:09 [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 https://mariadb.com/kb/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: 10.3.27-MariaDB-0+deb10u1
key_buffer_size=134217728
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 = 466214 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
