重启后，GRUB 2.04 启动，
第一个选项 UBUNTU 返回
/dev/nvme0n1p3: recovering journal
/dev/nvme0n1p3: clean, 138733/60022784 files, 189923044/240068608 blocks
[ 4.545063] cgroup1: Unknown parameter ‘memory_recursiveprot’
[ TIME ] Timed out waiting for device /dev/disk/by-uuid/C950-22C5
[DEPEND] Dependency failed for /boot/efi.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Clean up any mess left by 0dns-up.
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uuid/C950-22C5
[ TIME ] Timed out waiting for device /dev/disk/by-uuid/a7e6035e-774f-4faf-a97e-621fe9b51fa0.
[DEPEND] Dependency failed for /dev/disk/by-uuid/a7e6035e-774f-4faf-a97e-621fe9b51fa0.
[DEPEND] Dependency failed for Swaps.
[. 94.799333] proc: Bad value for ‘hidepid’
[FAILED] Failed to start Load Apparmor profiles.
You are in emergency mode.
After logging in, type "journalctl -xb" to view system logs,
"systemctl reboot" to reboot, "systemctl default"
or”exit” to boot into default mode.
Press Enter for maintenance
(Or press Control-D to continue):
journalctl 日志基本正常，只包含一些警告，并且重复出现了“等待设备消息超时”的情况/dev/disk/by-uuid/C950-22C5。/dev/disk/by-uuid/a7e6035e-774f-4faf-a97e-621fe9b51fa0
此外，还有一条红色cgroup2: Unknown parameter 'memory_recursiveprot'消息，还有另一条红色Failed to start AppArmor profiles.
df | grep -v loop
返回：
Filesystem 1K-blocks Used Available Use% Mounted on
udev 65758668 0 65758668 0% /dev
tmpfs 13158132 740 13157392 1% /run
/dev/nvme0n1p3 944074904 743369768 152675032 83% /
tmpfs 65790648 0 65790648 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
/dev/sdb1 15008576 11856 14996720 1% /usb
（手动连接 /usb 挂载以获取日志等）
blkid | grep -v 循环
返回
/dev/nvme0n1p1: UUID="C950-22C5" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="bad697e3-db9c-40e8-9b13-6599f5268208"
/dev/nvme0n1p2: UUID="a7e6035e-774f-4faf-a97e-621fe9b51fa0" TYPE="swap" PARTUUID="cefd1777-5563-44d1-80e2-5ddf0383ad73"
/dev/nvme0n1p3: UUID="55a10f71-7156-47e5-beaf-a3bc6f5437e7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ae5ea471-1a3d-46fc-99ad-a710074131a8"
/dev/sda: LABEL="Storage" UUID="74811583-21d7-495b-aaeb-eb48a30a4897" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdb1: UUID="28E8-161B" BLOCK_SIZE="512" TYPE="vfat"
并且 /etc/fstab 包含：
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p3 during installation
UUID=55a10f71-7156-47e5-beaf-a3bc6f5437e7 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=C950-22C5 /boot/efi vfat umask=0077 0 1
# swap was on /dev/nvme0n1p2 during installation
UUID=a7e6035e-774f-4faf-a97e-621fe9b51fa0 none swap sw 0 0
如果我运行，尽管启动时超时，仍会找到并连接磁盘mount -a。/boot/efi
我尝试了一些非侵入性的方法，例如安装驱动器、在 fstab 上注释掉磁盘等，但到目前为止，我尝试的任何方法仍然导致处于紧急模式。
我尝试让 grub 以恢复模式启动，但由于出现上述相同的错误而失败，让我陷入困境。
/boot/efi 在之后启动，这让mount -a我很困惑，这不就是启动时超时的原因吗？如果我可以轻松地从紧急模式手动安装它，那为什么在需要时它却不可用呢？
有人能帮我诊断问题或找到最小的修复方法吗？如果可能的话，我想避免重新安装操作系统。