尽管一些诊断工具（启动修复：在此报告）从 22.04 实时 USB（可能是 EFI）运行表明系统是 20.04 并且可能缺少 EFS 分区，它从来没有过（升级是在重启后从 18.04 运行的）。
仅在恢复模式下启动（在 grub 的 linux 命令行中将 recovery 替换为 rescue）才能提供 ~running~ 系统根控制台。这是因为我在恢复菜单中遇到了一些竞争条件，后台 systemctl 进程提示输入 Enter|Ctrl+D，同时需要键盘和屏幕（类似于这或者那）。
在那里（救援根控制台），我看到我的磁盘块设备都没有安装，但根（/）/dev/sda1grub 中 uuid 引用的文件系统。这里的主要问题似乎是我的正版/var那是在/dev/sdb3不可用。有没有办法让真正的 /var 在线，以便尝试 dpkg--配置-a以免我打dpkg：错误：无法访问 dpkg 的管理文件夹：没有此文件或文件夹？
请帮忙
[手动复制] journalctl 显示 3 个非常早期的错误（第 188-190 行）我认为与 AMD-Vi 无关
...
13:34:38 nux kernel: [Firmware bug]: AMD-Vi: IOAPIC[0] not in IVRS table
13:34:38 nux kernel: [Firmware bug]: AMD-Vi: No southbridge IOAPIC found
13:34:38 nux kernel: AMD-Vi: Disabling interrupt remapping
...
然后很久以后（第一个相关错误出现在第 801 行...就在“...设置主机名...”之后）
...
13:34:38 nux kernel: sda: sda1
...
13:34:38 nux kernel: sdb: sdb1 sdb2 sdb3
...
13:34:38 nux kernel: sdc: sdc1
...
13:34:38 nux kernel: ip_tables...
13:34:38 nux systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LICRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 +IDN +PCRE2 default-hierarchy=hybrid)
13:34:38 nux systemd[1]: Detected architecture x86-64
13:34:38 nux systemd[1]: Set hostname to <nux>
13:34:38 nux systemd[1]: /lib/systemd/system/systemd-udevd.service:26: Executable path is not absolute: udevadm control --reload --timeout 0
13:34:38 nux systemd[1]: /lib/systemd/system/systemd-udev-trigger.service:22: Executable path is not absolute: udevadm trigger --type=subsystems --action=add
13:34:38 nux systemd[1]: /lib/systemd/system/grub-common.service:10: Executable path is not absolute: grub-editenv /boot/grub/grubenv unset recordfail
13:34:38 nux systemd[1]: /lib/systemd/system/fstrim.service:18: Unknown system call group, ignoring: @system-service
13:34:38 nux systemd[1]: /lib/systemd/system/systemd-hwdb-update.service:25: Executable path is not absolute: systemd-hwdb update
13:34:38 nux systemd[1]: /lib/systemd/system/uuidd.service:21: Executable path is not absolute: Unknown system call group, ignoring: @system-service
13:34:38 nux systemd[1]: systemd-hwdb-update.service: Cannot add dependency job, ignoring: Unit systemd-hwdb-update.service is not loaded properly: Exec format error
13:34:38 nux kernel: random: systemd: uninitilized urandom read (16 bytes read)
...
13:34:38 nux kernel: EXT4-FS (sda1): remounted. Opts: errors=remount-ro
...
13:34:38 nux systemd-journald[300]: Journal started
13:34:38 nux systemd-journald[300]: Runtime journal (/run/log/journal/c8a.....) is 8.0M max 159.9M, 144.9M free.
...
13:34:38 nux systemd[1]: Started Set the console keyboard layout.
13:34:38 nux systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
13:34:38 nux systemd[1]: Reached target Local Encrypted Volumes.
13:34:38 nux systemd[1]: Reached target Local File Systems (Pre).
13:36:08 nux systemd[1]: dev-disk-by\x2duuid-ffac7b81\x2db405\x2d480b\x2d8681\x2d107e9ef9870a.device: Job dev-disk-by\x2duuid-ffac7b81\x2db405\x2d480b\x2d8681\x2d107e9ef9870a.device/start timed out.
13:36:08 nux systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-ffac7b81\x2db405\x2d480b\x2d8681\x2d107e9ef9870a.device.
13:36:08 nux systemd[1]: Dependency fail for /var.
...
13:36:08 nux systemd[1]: Starting Created Volatile Files and Directories...
13:36:08 nux systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
/home、/srv 和 Swap 也是如此。我对照 /etc/fstab 仔细检查了 UUID，没有问题。
非常感谢