我不小心拔掉了 NAS 的插头，插回后却无法启动，因为出现以下错误：
[ 105.556720] systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=11/SEGV
我已经设法进入紧急模式（root 没有定义密码，现在已经定义了），但我无法使日志服务工作。我不知道如何处理status=11/SEGV分段错误错误，因为我不知道意外断电导致内存寻址会出现什么问题？
root@syrenka-nas:~# systemctl status systemd-journald | cat
× systemd-journald.service - Journal Service
Loaded: loaded (/lib/systemd/system/systemd-journald.service; static)
Active: failed (Result: signal) since Tue 2023-08-29 13:01:31 CEST; 5min ago
TriggeredBy: × systemd-journald.socket
○ systemd-journald-audit.socket
○ systemd-journald-dev-log.socket
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Process: 343 ExecStart=/lib/systemd/systemd-journald (code=killed, signal=SEGV)
Main PID: 343 (code=killed, signal=SEGV)
FD Store: 0 (limit: 4224)
CPU: 92ms
该设备是 ReadyNAS Duo v2，操作系统是 Debian 12（从 11 升级），安装了一些来自测试分支的软件包。还需要注意的是，这是自将软件包更新到 Debian 12 (Bookworm) 和 Debian 13 (Trixie/testing) 以来的第一次重新启动
root@syrenka-nas:~# uname -a
Linux syrenka-nas 6.4.0-2-marvell #1 Debian 6.4.4-3 (2023-08-08) armv5tel GNU/Linux
root@syrenka-nas:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
事件发生后无法启动的系统服务：
root@syrenka-nas:~# systemctl --failed | cat
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-journal-flush.service loaded failed failed Flush Journal to Persistent Storage
● systemd-journald.service loaded failed failed Journal Service
● systemd-timesyncd.service loaded failed failed Network Time Synchronization
● systemd-udevd.service loaded failed failed Rule-based Manager for Device Events and Files
● systemd-journald.socket loaded failed failed Journal Socket
● systemd-udevd-control.socket loaded failed failed udev Control Socket
● systemd-udevd-kernel.socket loaded failed failed udev Kernel Socket
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
7 loaded units listed.
但我对它的理解是 systemd-journald.service 或 systemd-journald.socket 是启动失败的发起者。
我尝试手动启动服务并/var/log/journal/在紧急模式下清除目录，经过数十个小时的谷歌搜索后，我尝试更改日志设置：
PrivateDevices=no
NoNewPrivileges=no
但没有任何积极的结果。