![升级到 22.04 后服务 (systemd-modules-load.service +..) 损坏](https://linux22.com/image/1188840/%E5%8D%87%E7%BA%A7%E5%88%B0%2022.04%20%E5%90%8E%E6%9C%8D%E5%8A%A1%20(systemd-modules-load.service%20%2B..)%20%E6%8D%9F%E5%9D%8F.png)
刚刚一步步将我的服务器从 16.04 升级到 22.04。现在我遇到了这些超出我能力范围的问题。机器仍在运行。我该如何修复这些损坏的服务?或者,如果它们是多余的,我能否以某种方式删除它们?
$ sudo systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-modules-load.service loaded failed failed Load Kernel Modules
● ureadahead.service loaded failed failed Read required files in advance
● [email protected] loaded failed failed User Manager for UID 123
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.
3 loaded units listed.
$
$ systemctl status systemd-modules-load.service
× systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
Active: failed (Result: exit-code) since Sat 2022-08-20 13:33:48 BST; 7min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 18564 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 18564 (code=exited, status=1/FAILURE)
CPU: 9ms
Aug 20 13:33:48 bertha systemd[1]: Starting Load Kernel Modules...
Aug 20 13:33:48 bertha systemd-modules-load[18564]: Failed to insert module 'it87': Device or resource busy
Aug 20 13:33:48 bertha systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Aug 20 13:33:48 bertha systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Aug 20 13:33:48 bertha systemd[1]: Failed to start Load Kernel Modules.
$
$ systemctl status ureadahead.service
× ureadahead.service - Read required files in advance
Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-08-20 12:53:59 BST; 47min ago
Main PID: 275 (code=exited, status=5)
CPU: 7ms
Aug 20 12:53:59 bertha systemd[1]: ureadahead.service: Main process exited, code=exited, status=5/NOTINSTALLED
Aug 20 12:54:02 bertha ureadahead[275]: ureadahead: Error while tracing: No such file or directory
Aug 20 12:53:59 bertha systemd[1]: ureadahead.service: Failed with result 'exit-code'.
Notice: journal has been rotated since unit was started, output may be incomplete.
$
$ systemctl status [email protected]
× [email protected] - User Manager for UID 123
Loaded: loaded (/lib/systemd/system/[email protected]; static)
Drop-In: /usr/lib/systemd/system/[email protected]
└─10-oomd-user-service-defaults.conf, timeout.conf
Active: failed (Result: timeout) since Sat 2022-08-20 12:57:44 BST; 44min ago
Docs: man:[email protected](5)
Main PID: 943 (code=killed, signal=KILL)
Status: "Startup finished in 1min 5.193s."
CPU: 2.187s
Aug 20 12:57:44 bertha systemd[1]: [email protected]: Killing process 1294 (gmain) with signal SIGKILL.
Aug 20 12:57:44 bertha systemd[1]: [email protected]: Killing process 1295 (gdbus) with signal SIGKILL.
Aug 20 12:57:44 bertha systemd[1]: [email protected]: Killing process 1296 (dconf worker) with signal SIGKILL.
Aug 20 12:57:44 bertha systemd[1]: [email protected]: Killing process 1297 (pool-tracker-mi) with signal SIGKILL.
Aug 20 12:57:44 bertha systemd[1]: [email protected]: Main process exited, code=killed, status=9/KILL
Aug 20 12:57:44 bertha systemd[1]: [email protected]: Killing process 1293 (tracker-miner-f) with signal SIGKILL.
Aug 20 12:57:44 bertha systemd[1]: [email protected]: Failed with result 'timeout'.
Aug 20 12:57:44 bertha systemd[1]: [email protected]: Unit process 1293 (tracker-miner-f) remains running after unit stopped.
Aug 20 12:57:44 bertha systemd[1]: Stopped User Manager for UID 123.
Aug 20 12:57:44 bertha systemd[1]: [email protected]: Consumed 2.185s CPU time.
$
有关系统的一些信息..
$ lspci
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 01)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] (rev 01)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
$ lspci -k
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
Subsystem: ASUSTeK Computer Inc. 4 Series Chipset DRAM Controller
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 01)
Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 01)
Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 01)
Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 01)
Subsystem: ASUSTeK Computer Inc. P5B-MX/WiFi-AP, P5KPL-VM, P5LD2-VM Mainboard
Kernel driver in use: uhci_hcd
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 01)
Subsystem: ASUSTeK Computer Inc. P5B-MX/WiFi-AP, P5KPL-VM, P5LD2-VM Mainboard
Kernel driver in use: uhci_hcd
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 01)
Subsystem: ASUSTeK Computer Inc. P5B-MX/WiFi-AP, P5KPL-VM, P5LD2-VM Mainboard
Kernel driver in use: uhci_hcd
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 01)
Subsystem: ASUSTeK Computer Inc. P5B-MX/WiFi-AP, P5KPL-VM, P5LD2-VM Mainboard
Kernel driver in use: uhci_hcd
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 01)
Subsystem: ASUSTeK Computer Inc. P5B-MX/WiFi-AP, P5KPL-VM, P5LD2-VM Mainboard
Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
Subsystem: ASUSTeK Computer Inc. P5B-MX/WiFi-AP, P5KPL-VM Motherboard
Kernel driver in use: lpc_ich
Kernel modules: intel_rng, lpc_ich, leds_ss4200
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
Subsystem: ASUSTeK Computer Inc. P5B-MX/WiFi-AP, P5KPL-VM Motherboard
Kernel driver in use: ata_piix
Kernel modules: pata_acpi
00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] (rev 01)
Subsystem: ASUSTeK Computer Inc. P5B-MX/WiFi-AP, P5KPL-VM Motherboard
Kernel driver in use: ata_piix
Kernel modules: pata_acpi
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
Subsystem: ASUSTeK Computer Inc. M4A785/P7P55 Motherboard
Kernel driver in use: r8169
Kernel modules: r8169
$
答案1
作为一种通用方法,这些问题的解决方式与您报告的达到这一点的方式相同:“一步一步”。
我们从您的日志中挑选一条错误消息:“无法插入模块‘it87’:设备或资源繁忙”。第一个 Google 搜索结果是https://github.com/a1wong/it87/issues/1在该设备的存储库中有一个类似的标题。好兆头。您可以关注该主题,那里有不同的建议,适用于他们情况的建议如下:
我的情况通过添加 grub 配置得到解决
acpi_enforce_resources=lax
该解决方案得到了该来源的进一步评论的支持。
如果这不起作用,您需要继续挖掘。如果有效,您可以继续修复下一个错误。