Unable to restore Maria db database from backup file. Tried all 6 recovery modes but the result is same.

bash-4.2$ cat heuristic_recover.log
2021-10-02 1:22:15 0 [Note] InnoDB: Using Linux native AIO
2021-10-02 1:22:15 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-10-02 1:22:15 0 [Note] InnoDB: Uses event mutexes
2021-10-02 1:22:15 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2021-10-02 1:22:15 0 [Note] InnoDB: Number of pools: 1
2021-10-02 1:22:15 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-10-02 1:22:15 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-10-02 1:22:15 0 [Note] InnoDB: Completed initialization of buffer pool
2021-10-02 1:22:15 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-10-02 1:22:15 0 [Note] InnoDB: The log sequence number 98679815448 in the system tablespace does not match the log sequence number 98679815692 in the ib_logfiles!
2021-10-02 1:22:15 0 [Note] InnoDB: Last binlog file './nbp-cmdb-mariadb-0-bin.000050', position 403509723
2021-10-02 01:22:15 0x7f94b57b08c0 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.24/storage/innobase/btr/btr0pcur.cc line 471
InnoDB: Failing assertion: btr_page_get_prev(next_page) == btr_pcur_get_block(cursor)->page.id.page_no()
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.
211002 1:22:15 [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.24-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=2002
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4532509 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
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55a02a1c251e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55a029c57a4f]
sigaction.c:0(__restore_rt)[0x7f94b5397630]
:0(__GI_raise)[0x7f94b3668387]
:0(__GI_abort)[0x7f94b3669a78]
/usr/sbin/mysqld(+0x4ed8a0)[0x55a0299928a0]
/usr/sbin/mysqld(+0xacf407)[0x55a029f74407]
/usr/sbin/mysqld(+0xb263a6)[0x55a029fcb3a6]
/usr/sbin/mysqld(+0xb2a121)[0x55a029fcf121]
/usr/sbin/mysqld(+0xb2b07d)[0x55a029fd007d]
/usr/sbin/mysqld(+0xb2815e)[0x55a029fcd15e]
/usr/sbin/mysqld(+0xb2a121)[0x55a029fcf121]
/usr/sbin/mysqld(+0xb2b07d)[0x55a029fd007d]
/usr/sbin/mysqld(+0xb0efaa)[0x55a029fb3faa]
/usr/sbin/mysqld(+0xb0f173)[0x55a029fb4173]
/usr/sbin/mysqld(+0xb0f6c5)[0x55a029fb46c5]
/usr/sbin/mysqld(+0xa62bb2)[0x55a029f07bb2]
/usr/sbin/mysqld(+0x9519c1)[0x55a029df69c1]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x55a029c5a184]
/usr/sbin/mysqld(+0x5e1a60)[0x55a029a86a60]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x9ba)[0x55a029a87bea]
/usr/sbin/mysqld(+0x513897)[0x55a0299b8897]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x4ae)[0x55a0299bf2fe]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f94b3654555]
/usr/sbin/mysqld(+0x50d55d)[0x55a0299b255d]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /mariadb/data
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes unlimited unlimited processes
Max open files 1048576 1048576 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 1545308 1545308 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: core