dnf升级后,fedora 24无法启动

索贝克

昨晚,我对fedora 24 alpha安装进行了升级,今天第一次启动时,我刚得到了黑屏。

然后,我尝试启动进入救援模式,在显示fedora加载屏幕后,这给了我一个外壳。我尝试还原列出的最新更新dnf historylist undo id#,但由于未连接到网络而失败。

在外壳程序中,在提示输入root pwd之前,它显示了以下行:

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

有什么想法可以还原最近的更新吗?

编辑:

我浏览了提供的日志journalctl -xb,似乎有很多与挂载各种驱动器有关的systemd错误,所以这可能是它无法启动的原因。有趣的是,我的硬件设置没有发生任何变化,驱动器都按预期工作。

我忘了补充一点,我尝试启动到以前的两个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
米斯蒂夫

这对我有用。

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

selinux=1 enforcing=0

这将SELinux强制模式从严格设置宽松

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

本文收集自互联网,转载请注明来源。

如有侵权,请联系[email protected] 删除。

编辑于
0

我来说两句

0条评论
登录后参与评论

相关文章

来自分类Dev

升级后,Gnome无法在Fedora上启动,但gnome-classic确实能启动

来自分类Dev

从Fedora 23升级后,登录时Fedora 24触摸板不起作用

来自分类Dev

Fedora Core 24上的“ dnf install vidalia”?

来自分类Dev

Fedora无法启动。rub后黑屏

来自分类Dev

cygwin升级后X无法启动

来自分类Dev

升级后nuxeo服务无法启动

来自分类Dev

升级后将无法启动13.10

来自分类Dev

尝试升级后无法再启动Ubuntu

来自分类Dev

Ubuntu升级后qemu无法启动OpenWRT

来自分类Dev

升级后将无法启动13.10

来自分类Dev

RAM升级后系统无法启动

来自分类Dev

尝试升级后无法再启动Ubuntu

来自分类Dev

OSX Yosemite升级后,Apache无法启动

来自分类Dev

升级后无法启动Debian测试

来自分类Dev

应用升级后无法启动ubuntu

来自分类Dev

gui在dist升级后无法启动

来自分类Dev

内核升级后,Ubuntu无法启动

来自分类Dev

Windows升级后,grub无法启动

来自分类Dev

CPU升级后PC无法启动Windows

来自分类Dev

无法从USB启动Fedora

来自分类Dev

无法从USB启动Fedora

来自分类Dev

在Fedora 24上启动基准测试

来自分类Dev

安装Nvidia驱动程序后Fedora无法启动

来自分类Dev

升级到19.10后无法使用5.3.0内核启动

来自分类Dev

Nvidia驱动程序升级后,Ubuntu 12.10无法启动

来自分类Dev

升级后无法在Virtual Box中启动VM

来自分类Dev

升级Jenkins后,Jenkins无法启动通过SSH连接的从节点

来自分类Dev

升级3.3.3-1后,RabbitMQ将无法启动

来自分类Dev

升级Android Studio后,Executor Singleton无法启动