On Sat, 2019-11-09 at 23:00 +0800, Ed Greshko wrote: > On 11/9/19 10:42 PM, john.mellor@xxxxxxxxx wrote: > > I've had this problem ever since I moved up to Fedora 31 from > > Fedora > > 30. It fails to completely shutdown. It will reboot correctly, > > but > > not shutdown. It hangs with a frozen window showing a stalled > > rotating > > action indicator in Gnome, leaving the power on. > > > > The machine is an older Gateway core-i7 with 32GB ram, the original > > nVidia graphics card, and a larger SSD. Fedora 31 is fully up-to- > > date. > > > > How can I debug and/or fix this problem? Any ideas? > > First try. > > After rebooting, look at the end of the journal for the previous boot > to see if there are any messages > which may show a process hanging. > > You can use > > journalctl -b-1 -r > > The -b-1 says the previous boot log. -r says show in reverse time > order Git it. However, it is not showing any problems that I can see. Excerpt from the log showing a shutdown and subsequent powerup: === excerpt start === ov 08 19:14:18 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te> Nov 08 19:14:18 localhost.localdomain systemd[1]: Started Power-Off. Nov 08 19:14:18 localhost.localdomain systemd[1]: systemd-poweroff.service: Succeeded. Nov 08 19:14:18 localhost.localdomain systemd[1]: Reached target Final Step. Nov 08 19:14:18 localhost.localdomain systemd[1]: Reached target Shutdown. Nov 08 19:14:18 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina> Nov 08 19:14:18 localhost.localdomain systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Nov 08 19:14:18 localhost.localdomain systemd[1]: lvm2-monitor.service: Succeeded. Nov 08 19:14:18 localhost.localdomain lvm[14772]: 3 logical volume(s) in volume group "fedora_localhost-live" unmonitored Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdf: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sde: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdd: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdc: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdb: open failed: No medium found Nov 08 19:14:18 localhost.localdomain lvm[14772]: /dev/sdf: open failed: No medium found Nov 08 19:14:17 localhost.localdomain lvm[14772]: /dev/sde: open failed: No medium found Nov 08 19:14:17 localhost.localdomain lvm[14772]: /dev/sdd: open failed: No medium found Nov 08 19:14:17 localhost.localdomain lvm[14772]: /dev/sdc: open failed: No medium found Nov 08 19:14:17 localhost.localdomain lvm[14772]: /dev/sdb: open failed: No medium found Nov 08 19:14:17 localhost.localdomain systemd[1]: Stopped Create Static Device Nodes in /dev. Nov 08 19:14:17 localhost.localdomain systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded. Nov 08 19:14:17 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? > Nov 08 19:14:17 localhost.localdomain kernel: audit: type=1131 audit(1573258457.955:480): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck-root comm="systemd" exe="/usr/lib/systemd/> Nov 08 19:14:17 localhost.localdomain kernel: audit: type=1131 audit(1573258457.955:479): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd> Nov 08 19:14:17 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te> Nov 08 19:14:17 localhost.localdomain systemd[1]: Stopped File System Check on Root Device. Nov 08 19:14:17 localhost.localdomain systemd[1]: systemd-fsck-root.service: Succeeded. Nov 08 19:14:17 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? t> ...skipping... Nov 08 13:43:06 localhost.localdomain kernel: PCI: pci_cache_line_size set to 64 bytes Nov 08 13:43:06 localhost.localdomain kernel: PCI: Using ACPI for IRQ routing Nov 08 13:43:06 localhost.localdomain kernel: Registered efivars operations Nov 08 13:43:06 localhost.localdomain kernel: EDAC MC: Ver: 3.0.0 Nov 08 13:43:06 localhost.localdomain kernel: PTP clock support registered Nov 08 13:43:06 localhost.localdomain kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@xxxxxxxx> Nov 08 13:43:06 localhost.localdomain kernel: pps_core: LinuxPPS API ver. 1 registered === excerpt end === I guess its possible that something is not completing its shutdown step, but it does not appear to be logging that omission. Any idea how to isolate which is the faulty daemon? _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
