[root@stg-smpdb1 mariabkptest]# mariabackup --host=10.153.17.77 --user=root --password=root --port=33070 --socket=/tmp/mariadb_mysqld0.sock0 --datadir=/data1/mariadb/data0/ --target-dir=/nfsbackup/SMPDB/mariabkptest --prepare
mariabackup based on MariaDB server 10.3.9-MariaDB Linux (x86_64)
mariabackup: cd to /nfsbackup/SMPDB/mariabkptest/
mariabackup: This target seems to be not prepared yet.
mariabackup: using the following InnoDB configuration for recovery:
mariabackup:   innodb_data_home_dir = .
mariabackup:   innodb_data_file_path = ibdata1:10M:autoextend
mariabackup:   innodb_log_group_home_dir = .
mariabackup: Starting InnoDB instance for recovery.
mariabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
2022-09-13 16:32:13 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2022-09-13 16:32:13 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-09-13 16:32:13 0 [Note] InnoDB: Uses event mutexes
2022-09-13 16:32:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2022-09-13 16:32:13 0 [Note] InnoDB: Number of pools: 1
2022-09-13 16:32:13 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-09-13 16:32:13 0 [Note] InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M
2022-09-13 16:32:13 0 [Note] InnoDB: Completed initialization of buffer pool
2022-09-13 16:32:13 0 [Note] InnoDB: page_cleaner coordinator priority: -20
2022-09-13 16:32:13 0 [Note] InnoDB: Setting file './ibdata1' size to 10 MB. Physically writing the file full; Please wait ...
2022-09-13 16:32:13 0 [Note] InnoDB: File './ibdata1' size is now 10 MB.
2022-09-13 16:32:13 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes
2022-09-13 16:32:13 0x7fc0af1eb740  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/srv/srv0start.cc line 835
InnoDB: Failing assertion: !create_new_db || srv_operation == SRV_OPERATION_NORMAL
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/xtradbinnodb-recovery-modes/
InnoDB: about forcing recovery.
220913 16:32:13 [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.9-MariaDB
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_threads=1
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5572 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 0x49000
addr2line: 'mariabackup': No such file
mariabackup(my_print_stacktrace+0x2b)[0x55b5a2f5c1eb]
mariabackup(handle_fatal_signal+0x537)[0x55b5a2a98d47]
sigaction.c:0(__restore_rt)[0x7fc0aedcd5e0]
:0(__GI_raise)[0x7fc0adbe11f7]
:0(__GI_abort)[0x7fc0adbe28e8]
addr2line: 'mariabackup': No such file
mariabackup(+0x539a45)[0x55b5a278ca45]
mariabackup(+0xb4793d)[0x55b5a2d9a93d]
mariabackup(+0xb49341)[0x55b5a2d9c341]
mariabackup(+0x55f784)[0x55b5a27b2784]
mariabackup(main+0x185)[0x55b5a278ee65]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fc0adbcdc05]
addr2line: 'mariabackup': No such file
mariabackup(+0x556919)[0x55b5a27a9919]
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.
Aborted
[root@stg-smpdb1 mariabkptest]#