我的问题是。为什么它突然无法启动？这种情况是不是偶尔会发生？以下是背景。
在一台关机的电脑上，正常关机一天后，它停留在空白屏幕上，底部有 Ubuntu 徽标。我正在运行桌面版 20.04。它以前也出现过一次这种情况。首先，我只是使用可启动的 USB 驱动器重新安装了操作系统。我最近安装了它，所以我没有什么可失去的，只是把它归咎于我是 Linux 新手。
因此，当第二次发生这种情况时，在我投入更多精力处理文档和安装更多应用程序后，我重新启动并选择恢复模式。然后它执行了一些进程，我继续恢复启动。系统以最少的服务启动。我再次重新启动，它正常启动。
电脑是定制的，但相当基础。英特尔 i5 第 9 代，无显卡（使用集成显卡），500 GB 固态硬盘，华硕 z390-p 主板，32 GB 内存。
问题又来了：为什么它突然无法启动？这种情况是不是时不时就会发生？
@heynnema 请求的数据
jbunke@J-Bunke-Enterprises:~$ free -h
total used free shared buff/cache available
Mem: 31Gi 5.5Gi 21Gi 820Mi 3.8Gi 24Gi
Swap: 979Mi 0B 979Mi
jbunke@J-Bunke-Enterprises:~$ sysctl vm.swappiness
vm.swappiness = 60
jbunke@J-Bunke-Enterprises:~$ sudo lshw -C memory
[sudo] password for jbunke:
*-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: 2808
date: 05/27/2020
size: 64KiB
capacity: 16MiB
capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
*-memory
description: System Memory
physical id: 3f
slot: System board or motherboard
size: 32GiB
*-bank:0
description: [empty]
physical id: 0
slot: ChannelA-DIMM1
*-bank:1
description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns)
product: BL16G32C16U4B.M16FE
vendor: CRUCIAL
physical id: 1
serial: E44E9AD5
slot: ChannelA-DIMM2
size: 16GiB
width: 64 bits
clock: 2666MHz (0.4ns)
*-bank:2
description: [empty]
physical id: 2
slot: ChannelB-DIMM1
*-bank:3
description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns)
product: BL16G32C16U4B.M16FE
vendor: CRUCIAL
physical id: 3
serial: E44E9EE2
slot: ChannelB-DIMM2
size: 16GiB
width: 64 bits
clock: 2666MHz (0.4ns)
*-cache:0
description: L1 cache
physical id: 4a
slot: L1 Cache
size: 384KiB
capacity: 384KiB
capabilities: synchronous internal write-back unified
configuration: level=1
*-cache:1
description: L2 cache
physical id: 4b
slot: L2 Cache
size: 1536KiB
capacity: 1536KiB
capabilities: synchronous internal write-back unified
configuration: level=2
*-cache:2
description: L3 cache
physical id: 4c
slot: L3 Cache
size: 9MiB
capacity: 9MiB
capabilities: synchronous internal write-back unified
configuration: level=3
*-memory UNCLAIMED
description: RAM memory
product: Cannon Lake PCH Shared SRAM
vendor: Intel Corporation
physical id: 14.2
bus info: pci@0000:00:14.2
version: 10
width: 64 bits
clock: 33MHz (30.3ns)
capabilities: pm cap_list
configuration: latency=0
resources: memory:a1316000-a1317fff memory:a131c000-a131cfff
@heynnema 请求更多数据
jbunke@J-Bunke-Enterprises:~$ cat /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>
/dev/mapper/vgubuntu-root / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=FEDE-412A /boot/efi vfat umask=0077 0 1
/dev/mapper/vgubuntu-swap_1 none swap sw 0 0
jbunke@J-Bunke-Enterprises:~$ cat /etc/initramfs-tools/conf.d/resume
cat: /etc/initramfs-tools/conf.d/resume: No such file or directory
jbunke@J-Bunke-Enterprises:~$ cat /etc/initramfs-tools/conf.d/resume
cat: /etc/initramfs-tools/conf.d/resume: No such file or directory
jbunke@J-Bunke-Enterprises:~$ sudo blkid
[sudo] password for jbunke:
/dev/mapper/vgubuntu-swap_1: UUID="7ffeabb5-c0a1-4ab5-b3c8-5222d5c0a600" TYPE="swap"
/dev/mapper/vgubuntu-root: UUID="661fbc14-52e0-49a9-9650-7c76eb668dd7" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/nvme0n1p1: UUID="FEDE-412A" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="ccb025e7-c65f-42ab-a8d3-939facad99cc"
/dev/nvme0n1p2: UUID="rs9tDP-TTZ3-j6kO-lCqt-YDzE-q3yT-boj3bB" TYPE="LVM2_member" PARTUUID="209c89dc-9071-450c-a2ca-6d1e5d0e5f4a"
/dev/sda1: LABEL="PQSERVICE" UUID="00847BE3847BDA1C" TYPE="ntfs" PARTUUID="691acec4-01"
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="94C87C71C87C5388" TYPE="ntfs" PARTUUID="691acec4-02"
/dev/sda3: LABEL="Gateway" UUID="06DC7E0FDC7DF8EF" TYPE="ntfs" PARTUUID="691acec4-03"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
jbunke@J-Bunke-Enterprises:~$ grep "GRUB_" /etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
#GRUB_TERMINAL=console
#GRUB_GFXMODE=640x480
#GRUB_DISABLE_LINUX_UUID=true
#GRUB_DISABLE_RECOVERY="true"
#GRUB_INIT_TUNE="480 440 1"
jbunke@J-Bunke-Enterprises:~$
答案1
我有多个显示器，当系统尝试启动时，两个显示器都打开时，就会出现启动问题。我将使用的解决方法是在启动时关闭辅助显示器。系统启动后，辅助显示器打开，它就可以正常工作了。
我不确定它是否应该在两个显示器都打开的情况下启动，但这种解决方法对我来说没问题，而且不值得尝试让它在两个显示器都打开的情况下工作。
更新 - 我发现我需要从后面板拔下视频线，否则系统将无法启动。仅关闭显示器是不够的。现在这种解决方法并不理想，我将进一步研究为什么在连接 2 个显示器的情况下系统无法启动。