Bonjour,

Eh bien le répit aura été de courte durée : me revoilà en mode urgence alors qu'hier tout se passait bien (kde, personnalisation de thème, jeu Counter-Strike sans aucun problème).
Je n'ai pas la moindre idée de comment savoir d'où vient le problème et à vrai dire je suis tellement dépité que je n'arrive plus à réfléchir. Ça fait seulement 3 jours de batailles (cf sujet : Problème driver NVIDIA GeForce GT 560 Ti) pour avoir un système toujours en panne.

Any suggestion ?
C'est quoi le mode urgence pour toi ? Une photo peut-être pour nous aider.
Après une longue tentative de démarrage (ça reste un moment sur les 3 petits carrés du démarrage), je suis ramené à la console que le système appelle "emergency mode". Le système m'invite à saisir "journalctl -xb" pour voir la log, "systemctl default" pour retenter le lancement de la session graphique.

Au cas où, je vous transmets le résultat des commandes :

journalctl -xb | tail -n 50 
Aug 18 15:53:21 tron.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auditd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 18 15:53:21 tron.localdomain systemd[1]: Starting Update UTMP about System Boot/Shutdown...
-- Subject: Unit systemd-update-utmp.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-update-utmp.service has begun starting up.
Aug 18 15:53:21 tron.localdomain audit[982]: SYSTEM_BOOT pid=982 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Aug 18 15:53:21 tron.localdomain systemd[1]: Started Update UTMP about System Boot/Shutdown.
-- Subject: Unit systemd-update-utmp.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-update-utmp.service has finished starting up.
-- 
-- The start-up result is done.
Aug 18 15:53:21 tron.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 18 15:53:21 tron.localdomain systemd[1]: Starting Update UTMP about System Runlevel Changes...
-- Subject: Unit systemd-update-utmp-runlevel.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-update-utmp-runlevel.service has begun starting up.
Aug 18 15:53:21 tron.localdomain systemd[1]: Started Update UTMP about System Runlevel Changes.
-- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-update-utmp-runlevel.service has finished starting up.
-- 
-- The start-up result is done.
Aug 18 15:53:21 tron.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 18 15:53:21 tron.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 18 15:53:21 tron.localdomain systemd[1]: Startup finished in 18.377s (kernel) + 2.673s (initrd) + 1min 34.430s (userspace) = 1min 55.480s.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- All system services necessary queued for starting at boot have been
-- started. Note that this does not mean that the machine is now idle as services
-- might still be busy with completing start-up.
-- 
-- Kernel start-up required 18377205 microseconds.
-- 
-- Initial RAM disk start-up required 2673308 microseconds.
-- 
-- Userspace start-up required 94430381 microseconds.
Aug 18 15:53:22 tron.localdomain systemd[1]: Received SIGRTMIN+21 from PID 426 (plymouthd).
Aug 18 15:53:22 tron.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 18 15:53:22 tron.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dmesg | tail -n 50 
[   31.992997] intel_rapl: Found RAPL domain core
[   31.993000] intel_rapl: RAPL package 0 domain package locked by BIOS
[   32.007950] kauditd_printk_skb: 4 callbacks suppressed
[   32.007951] audit: type=1130 audit(1503064896.510:66): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   32.122117] nvidia: module license 'NVIDIA' taints kernel.
[   32.122118] Disabling lock debugging due to kernel taint
[   32.128379] nvidia 0000:02:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[   32.128426] nvidia-nvlink: Nvlink Core is being initialized, major device number 239
[   32.128433] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 PDT 2017 (using threaded interrupts)
[   32.160676] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  375.66  Mon May  1 14:33:30 PDT 2017
[   32.183057] usbcore: registered new interface driver snd-usb-audio
[   32.343536] Bluetooth: Core ver 2.22
[   32.343549] NET: Registered protocol family 31
[   32.343550] Bluetooth: HCI device and connection manager initialized
[   32.343553] Bluetooth: HCI socket layer initialized
[   32.343555] Bluetooth: L2CAP socket layer initialized
[   32.343558] Bluetooth: SCO socket layer initialized
[   32.444169] [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver
[   32.444170] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:02:00.0 on minor 0
[   32.468777] usbcore: registered new interface driver btusb
[   32.937523] Adding 2097148k swap on /dev/mapper/fedora_tron-swap.  Priority:-1 extents:1 across:2097148k FS
[   33.133327] audit: type=1130 audit(1503064897.635:67): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   33.197366] audit: type=1130 audit(1503064897.699:68): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-settle comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   33.728628] audit: type=1130 audit(1503064898.230:69): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.245083] audit: type=1130 audit(1503064899.747:70): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dmraid-activation comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.245086] audit: type=1131 audit(1503064899.747:71): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dmraid-activation comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.476381] audit: type=1130 audit(1503064899.978:72): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sda1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.693651] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   35.771740] audit: type=1130 audit(1503064900.274:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sde2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.772001] audit: type=1130 audit(1503064900.274:74): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sdc2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   35.772279] audit: type=1130 audit(1503064900.274:75): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sdc5 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   36.114370] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)
[   36.162967] fuse init (API version 7.26)
[   36.647055] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[   37.877556] kauditd_printk_skb: 4 callbacks suppressed
[   37.877559] audit: type=1131 audit(1503064902.379:80): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.477779] audit: type=1130 audit(1503064977.984:81): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iscsi-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.610567] audit: type=1130 audit(1503064978.117:82): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.610745] audit: type=1130 audit(1503064978.117:83): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=blk-availability comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.627244] audit: type=1130 audit(1503064978.134:84): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfs-config comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.627247] audit: type=1131 audit(1503064978.134:85): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=nfs-config comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.706665] audit: type=1130 audit(1503064978.213:86): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.706667] audit: type=1131 audit(1503064978.213:87): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.728034] audit: type=1130 audit(1503064978.234:88): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpc-statd-notify comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.728036] audit: type=1131 audit(1503064978.234:89): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=rpc-statd-notify comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.768470] audit: type=1130 audit(1503064978.275:90): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fedora-import-state comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[  113.978547] RPC: Registered named UNIX socket transport module.
[  113.978548] RPC: Registered udp transport module.
[  113.978548] RPC: Registered tcp transport module.
[  113.978549] RPC: Registered tcp NFSv4.1 backchannel transport module.
Ok, le problème est résolu. En parcourant la checklist de démarrage, j'ai constaté des erreurs au niveau d'une partition montée par la fstab : cette partition a été supprimée hier au cours d'un nettoyage et d'une réorganisation de mes disques.
J'ai supprimé l'entrée correspondante dans mon fstab et tout est rentré dans l'ordre.

Merci tout de même Nicosss pour ton intérêt 😉.

Sujet résolu.
Bon tant pis j'arrive trop tard, par contre pense à mettre les logs en entier car les 50 derniers évènements ne sont pas toujours parlant, même si dès fois ce n'est pas parlant tout compte fait :-D
Ok Nicosss, je ne voulais juste pas saturer avec de l'hyper-verbeux.