Ontem à noite eu fiz um upgrade no meu fedora 24 alpha install e quando inicializo pela primeira vez hoje eu acabei com uma tela preta.
Então eu tentei inicializar no modo de recuperação, o que me deixou com um shell depois de mostrar a tela de carregamento do fedora. Tentei reverter a última atualização listada com dnf historylist undo id# , mas isso falhou porque não se conecta à rede.
No shell, mostra essa linha antes de solicitar pwd root:
dracut-pre-udev[302]: Symbol 'svc_auth_none' has different size in shared object, consider relinking
Alguma idéia de como eu poderia reverter a última atualização?
Examinei o log fornecido por journalctl -xb e parece haver muitos erros de systemd relacionados à montagem de todos os tipos de unidades, de modo que essa é provavelmente a razão pela qual ele não inicializa. O engraçado é que minha configuração de hardware não mudou um bit, as unidades estão todas funcionando como deveria.
Esqueci-me de acrescentar que tentei arrancar nas duas versões anteriores do kernel alfa sem sucesso (apesar de ambos terem trabalhado antes da actualização de ontem).
Ouput de 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.
Conteúdo de /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
Isso funcionou para mim.
Adicione o seguinte ao seu parâmetro do kernel.
selinux=1 enforcing=0
Isso define o modo de imposição do SELinux de strict para permissivo .
Esta é uma solução temporária até eu descobrir o que está acontecendo ou até que uma atualização corrija o problema.
Espero que ajude.
A solução que usei foi
setenforce 0 systemctl isolate graphical Isso é causado por um bug na política do SELinux. Consulte o link - em 2 de maio de 2016, há um atualização no teste que deve resolver o problema.
Nesse meio tempo, a inicialização com enforcing=0 resolverá o problema.