Debian Bullseye环境下MariaDB从10.11.4升级至11.0.2后无法启动的问题求助

各位好，我现在碰到了个棘手的问题：我在Debian Bullseye系统上尝试把MariaDB从10.11.4版本升级到11.0.2版本，但升级完成后服务根本启动不起来。

我用systemctl status mariadb.service和journalctl -xe查看状态，得到的信息非常有限，具体输出如下：

● mariadb.service - MariaDB 11.0.2 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: inactive (dead) (Result: signal) since Fri 2023-06-16 22:05:13 CEST; 4s ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 6291 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCE>
Process: 6292 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCC>
Process: 6294 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/>
Process: 6323 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, si>
Main PID: 6323 (code=killed, signal=ABRT)
CPU: 144ms

Jun 16 22:05:10 XXXXX mariadbd[6323]: Max processes             128262               128262               processes
Jun 16 22:05:10 XXXXX mariadbd[6323]: Max open files            32768                32768                files
Jun 16 22:05:10 XXXXX mariadbd[6323]: Max locked memory         524288               524288               bytes
Jun 16 22:05:10 XXXXX mariadbd[6323]: Max address space         unlimited            unlimited            bytes
Jun 16 22:05:10 XXXXX mariadbd[6323]: Max file locks            unlimited            unlimited            locks
Jun 16 22:05:10 XXXXX mariadbd[6323]: Max pending signals       128262               128262               signals
Jun 16 22:05:10 XXXXX mariadbd[6323]: Max msgqueue size         819200               819200               bytes
Jun 16 22:05:10 XXXXX mariadbd[6323]: Max nice priority         0                    0
Jun 16 22:05:10 XXXXX mariadbd[6323]: Max realtime priority     0                    0
Jun 16 22:05:10 XXXXX mariadbd[6323]: Max realtime timeout      unlimited            unlimited            us
Jun 16 22:05:10 XXXXX mariadbd[6323]: Core pattern: core
Jun 16 22:05:10 XXXXX mariadbd[6323]: Kernel version: Linux version 5.10.0-23-amd64 (debian-kernel@lists.debian.org) >
Jun 16 22:05:10 XXXXX systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit mariadb.service has exited.
░░
░░ The process' exit code is 'killed' and its exit status is 6.
Jun 16 22:05:10 XXXXX systemd[1]: mariadb.service: Failed with result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit mariadb.service has entered the 'failed' state with result 'signal'.
Jun 16 22:05:10 XXXXX systemd[1]: Failed to start MariaDB 11.0.2 database server.
░░ Subject: A start job for unit mariadb.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit mariadb.service has finished with a failure.
░░
░░ The job identifier is 6703 and the job result is failed.

本来想通过错误日志进一步排查，但奇怪的是，我已经设置了log_error=/var/log/mysql/error.log，还检查了Debian默认配置里所有的skip_log_error和syslog相关设置，MariaDB就是不肯输出错误日志。

另外，如果我把/var/lib/mysql重命名，然后重新初始化数据库，服务就能正常启动了——但这对我来说完全不是解决方案，因为我需要恢复原有的数据，而且这次刚好没备份，真的很头疼。

有没有大佬能给点思路或者可行的解决办法？

备注：内容来源于stack exchange，提问作者Chaeska