我最近在一台旧笔记本电脑上安装了 Arch Linux，我将其用作个人工作站和机器，以更好地学习如何管理 Linux。
自从我安装了 Arch Linux 以来，我就开始出现持续性的启动失败，但这种情况只在其他启动时发生。当这种情况发生时，我为 /var 挂载创建的 LVM 卷上的 Systemd.fsck 作业会超时，此时它会进入紧急模式。到目前为止，我刚刚重新启动，但它很烦人，所以我想我会在这里发布我能发布的内容，看看问题是否明显。
没有其他操作系统，我使用 Grub 作为引导加载程序。下面列出了分区表。
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 47G 2.7G 42G 7% /
dev 1.8G 0 1.8G 0% /dev
run 1.8G 468K 1.8G 1% /run
tmpfs 1.8G 0 1.8G 0% /dev/shm
tmpfs 1.8G 0 1.8G 0% /sys/fs/cgroup
tmpfs 1.8G 8.0K 1.8G 1% /tmp
/dev/mapper/volgrp1-lv_var 20G 1.1G 18G 6% /var
/dev/sda1 656M 46M 563M 8% /boot
/dev/mapper/volgrp1-lv_home 227G 1.5G 214G 1% /home
tmpfs 356M 4.0K 356M 1% /run/user/1000
这是启动失败的journalctl的相关部分：
Jan 22 22:03:33 dustin-laptop kernel: USB Video Class driver (1.1.1)
Jan 22 22:03:33 dustin-laptop lvm[205]: 2 logical volume(s) in volume group "volgrp1" now active
Jan 22 22:04:57 dustin-laptop systemd[1]: Job dev-mapper-volgrp1\x2dlv_home.device/start timed out.
Jan 22 22:04:57 dustin-laptop systemd[1]: Timed out waiting for device dev-mapper-volgrp1\x2dlv_home.device.
Jan 22 22:04:57 dustin-laptop systemd[1]: Dependency failed for /home.
Jan 22 22:04:57 dustin-laptop systemd[1]: Dependency failed for Local File Systems.
Jan 22 22:04:57 dustin-laptop systemd[1]: Job dev-mapper-volgrp1\x2dlv_var.device/start timed out.
Jan 22 22:04:57 dustin-laptop systemd[1]: Timed out waiting for device dev-mapper-volgrp1\x2dlv_var.device.
Jan 22 22:04:57 dustin-laptop systemd[1]: Dependency failed for /var.
Jan 22 22:04:57 dustin-laptop systemd[1]: Dependency failed for Load/Save Random Seed.
Jan 22 22:04:57 dustin-laptop systemd[1]: Dependency failed for Update UTMP about System Boot/Shutdown.
Jan 22 22:04:57 dustin-laptop systemd[1]: Dependency failed for Trigger Flushing of Journal to Persistent Storage.
Jan 22 22:04:57 dustin-laptop systemd[1]: Dependency failed for Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Jan 22 22:04:57 dustin-laptop systemd[1]: Dependency failed for Load/Save RF Kill Switch Status of rfkill0.
Jan 22 22:04:57 dustin-laptop alsactl[237]: /usr/bin/alsactl: load_state:1677: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
Jan 22 22:04:57 dustin-laptop alsactl[237]: /usr/bin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid
Jan 22 22:04:57 dustin-laptop alsactl[237]: Found hardware: "HDA-Intel" "IDT 92HD81B1X5" "HDA:111d7605,103c169a,00100107" "0x103c" "0x169a"
Jan 22 22:04:57 dustin-laptop alsactl[237]: Hardware is initialized using a generic method
Jan 22 22:04:58 dustin-laptop kernel: microcode: CPU0: new patch_level=0x05000119
Jan 22 22:04:58 dustin-laptop kernel: microcode: CPU1: new patch_level=0x05000119
Jan 22 22:04:58 dustin-laptop systemd[239]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
现在这里是与干净启动时 LVM var 挂载相关的相同相关部分：
Jan 22 22:20:10 dustin-laptop kernel: rt2800pci 0000:06:00.0 wlo1: renamed from wlan0
Jan 22 22:20:11 dustin-laptop systemd-fsck[196]: /dev/sda1: clean, 360/43776 files, 18545/174744 blocks
Jan 22 22:20:11 dustin-laptop systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway.
-- Subject: Mount point is not empty
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The directory /var is specified as the mount point (second field in
-- /etc/fstab or Where= field in systemd unit file) and is not empty.
-- This does not interfere with mounting, but the pre-exisiting files in
-- this directory become inaccessible. To see those over-mounted files,
-- please manually mount the underlying file system to a secondary
-- location.
Jan 22 22:20:11 dustin-laptop kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: data=ordered
Jan 22 22:20:12 dustin-laptop kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: data=ordered
Jan 22 22:20:12 dustin-laptop systemd-journal[140]: Permanent journal is using 80.0M (max allowed 1.9G, trying to leave 2.9G free of 17.5G available → current limit 1.9G).
Jan 22 22:20:13 dustin-laptop systemd-journal[140]: Time spent on flushing to /var is 475.798ms for 699 entries.
Jan 22 22:20:14 dustin-laptop kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: data=ordered
Jan 22 22:20:14 dustin-laptop kernel: media: Linux media interface: v0.10
Jan 22 22:20:14 dustin-laptop kernel: Linux video capture interface: v2.00
Jan 22 22:20:14 dustin-laptop kernel: uvcvideo: Found UVC 1.00 device HP Truevision HD (05c8:0348)
Jan 22 22:20:14 dustin-laptop kernel: input: HP Truevision HD as /devices/pci0000:00/0000:00:13.2/usb2/2-1/2-1:1.0/input/input18
Jan 22 22:20:14 dustin-laptop kernel: usbcore: registered new interface driver uvcvideo
Jan 22 22:20:14 dustin-laptop kernel: USB Video Class driver (1.1.1)
Jan 22 22:20:14 dustin-laptop lvm[195]: 2 logical volume(s) in volume group "volgrp1" now active
Jan 22 22:20:14 dustin-laptop kernel: microcode: CPU0: new patch_level=0x05000119
Jan 22 22:20:14 dustin-laptop kernel: microcode: CPU1: new patch_level=0x05000119
现在我碰巧注意到，在根挂载点上，其 /var 目录中似乎已经有文件，并且它会发出这样的警告。我不确定为什么会这样，但我想知道这是否可能与这里问题的原因有关。如果相关，我应该如何修复它？只有 47GB 分配给根分区，我知道日志和日记如何变得相当大。我更喜欢他们分开。你怎么看？
如果您还想查看我的 fstab 文件，请告诉我。