20.04 LTS不会启动: systemd-logind.service未能将stdout连接到日志套接字，并且在引导过程中出现了许多故障

Question

幸运的是，我有NYUbuntu20.04服务器的快照，因为当我重新启动它时，在bootI期间会看到许多服务出现故障，然后在systemd- during上挂起。服务未能将stdout连接到日志套接字。

引导期间的

错误：

引导后的

雄：

如果我回滚到快照(在重新启动之前，它仍在工作)：

系统日志显示：

Feb 01 16:46:31 socwk multipathd[748]: sda: failed to get udev uid: Invalid argument
Feb 01 16:46:31 socwk multipathd[748]: sda: failed to get sysfs uid: Invalid argument
Feb 01 16:46:31 socwk multipathd[748]: sda: failed to get sgio uid: No such file or directory

systemctl给出：

● fwupd-refresh.service                                                                            loaded failed failed    Refresh fwupd metadata and update motd  
systemd-hostnamed.service                                                                        loaded failed failed    Hostname Service   

如果我试图在重新启动之前安装更新，我会得到以下错误：

Installing new version of config file /etc/systemd/resolved.conf ...
Job for systemd-networkd.service failed because the control process exited with error code.
See "systemctl status systemd-networkd.service" and "journalctl -xe" for details.
Job for systemd-resolved.service failed.
See "systemctl status systemd-resolved.service" and "journalctl -xe" for details.
Job for systemd-journald.service failed.
See "systemctl status systemd-journald.service" and "journalctl -xe" for details.
Setting up netplan.io (0.101-0ubuntu3~20.04.2) ...
Setting up systemd-timesyncd (245.4-4ubuntu3.4) ...
Job for systemd-timesyncd.service failed.

以及：

Errors were encountered while processing:
 udev
 mdadm
 ubuntu-drivers-common
 ubuntu-minimal

我真的不知道该从哪里着手解决这个问题。

Answer 1

此问题可能由根目录/遭受所有权或权限更改所致。它通常应该(至少在Ubuntu下)由具有755权限的root:root拥有。如果这是错误的，您可以用

chown root:root / && chmod 755 /

那就重新启动。