☰

Fedora 24 在 dnf 升级后无法启动

tag-icon • tag-icon fedora boot dnf
Fedora 24 在 dnf 升级后无法启动

昨晚我对 Fedora 24 alpha 安装进行了升级，今天第一次启动时，我只是遇到了黑屏。

然后我尝试启动救援模式，在显示 Fedora 加载屏幕后，我只剩下一个 shell。我尝试恢复列出的最新更新dnf historylist undo id#，但失败了，因为它无法连接到网络。

在 shell 中，它在提示输入 root pwd 之前显示此行：

dracut-pre-udev[302]: Symbol 'svc_auth_none' has different size in shared object, consider relinking

有什么想法可以恢复上次更新吗？

编辑：

我查看了提供的日志journalctl -xb，似乎有很多与安装各种驱动器相关的系统错误，所以这可能是它无法启动的原因。有趣的是，我的硬件设置没有改变一点，驱动器都按预期工作。

我忘记补充一点，我尝试启动到之前的两个 alpha 内核版本，但没有成功（尽管这两个版本在昨天的更新之前都可以工作）。

编辑2：

输出journalctl -xb -p3：

    -- Logs begin at Mit 2016-01-20 15:01:49 CET, end at Fre 2016-04-29 17:06:53 CEST. --
Apr 29 19:06:48 localhost systemd[1]: Device dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1
Apr 29 19:06:48 localhost systemd[1]: Device dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2 and /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd/sdd1
Apr 29 19:06:48 localhost systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2 and /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd/sdd4
Apr 29 19:06:50 localhost rpcbind[314]: cannot open file = /tmp/rpcbind.xdr for writing
Apr 29 19:06:50 localhost rpcbind[314]: cannot save any registration
Apr 29 19:06:50 localhost rpcbind[314]: cannot open file = /tmp/portmap.xdr for writing
Apr 29 19:06:50 localhost rpcbind[314]: cannot save any registration
Apr 29 17:06:50 linux.fritz.box systemd[1]: Failed to mount NFSD configuration filesystem.
-- Subject: Unit proc-fs-nfsd.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit proc-fs-nfsd.mount has failed.
-- 
-- The result is failed.
Apr 29 17:06:50 linux.fritz.box systemd[1]: dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1 and /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
Apr 29 17:06:51 linux.fritz.box systemd[1]: dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device: Dev dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2 and /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd/sdd1
Apr 29 17:06:51 linux.fritz.box systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2 and /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd/sdd4
Apr 29 17:06:51 linux.fritz.box systemd[1]: Failed to mount /boot/efi.
-- Subject: Unit boot-efi.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit boot-efi.mount has failed.
-- 
-- The result is failed.
Apr 29 17:06:53 linux.fritz.box systemd[1]: Failed to mount /mnt/20DF1A322D28FF74.
-- Subject: Unit mnt-20DF1A322D28FF74.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mnt-20DF1A322D28FF74.mount has failed.
-- 
-- The result is failed.

编辑3：

内容/etc/systemd/system/default.target

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Graphical Interface
Documentation=man:systemd.special(7)
Requires=multi-user.target
Wants=display-manager.service
Conflicts=rescue.service rescue.target
After=multi-user.target rescue.service rescue.target display-manager.service
AllowIsolate=yes

答案1

这对我有用。

将以下内容添加到您的内核参数中。

selinux=1 enforcing=0

这将 SELinux 强制模式设置为严格的到宽容的。

这是一个临时解决方案，直到我弄清楚发生了什么，或者更新解决问题为止。

答案2

我使用的解决方案是

  1. 将 default.target 更改为 multi-user.target （是图形化的。）
  2. setenforce 0
  3. systemctl isolate graphical

答案3

为了完整起见，我将补充一点，这是版本 3.13.1-183.fc24 的selinux-policy问题selinux-policy-targeted。将这些版本降级到以前的版本或使用 3.13.1-184.fc24 可以修复此问题。

另请参阅 bugzilla 条目这里和这里。

答案4

这是由 SELinux 策略中的错误引起的。看https://bugzilla.redhat.com/show_bug.cgi?id=1331668— 截至 2016 年 5 月 2 日，有测试中更新这应该可以解决问题。

与此同时，启动 withenforcing=0将解决该问题。

相关内容