On Tue, 02 Jan 2018 20:06:24 +0100 Martin Wagner <martin.wagner@xxxxxxxxxx> wrote: > Since some time back I can no longer do a software update using Gnome > Software (version 3.24.3) on my Fedora 26 desktop. Using 'yum update' > works fine. What happens is that when I hit the 'Restart & Update' > button I'm not sure I understand: Do you use the command line update system (yum/dnf) back to back with the Gnome Software upgrade routine? IINM Gnome software has its own update system independently from tools like dnf ... > the system is going down and there are some log messages that > flicker by really quickly. Then at bootup after unlocking the disk > there are again some log messages that flicker by quickly. What I > managed to see from the messages is the the phrase 'Device or resource > busy'. After that the system reboots and comes up normally but without > any software updates applied. > > I'll attach the end of journald when the system is going down first > time. There are some error, but I don't know what to make of them... > > My biggest concern is not really about software update, as yum update > works fine, but about doing a fedup to Fedora 27 at some point. That > would probably not work? > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-d1a72941\x2deb0a\x2d4d82\x2d96ae\x2df837c572b875 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > systemd[1]: Stopped File System Check on /dev/disk/by-uuid/d1a72941-eb0a-4d82-96ae-f837c572b875. > systemd[1]: Removed slice system-systemd\x2dfsck.slice. > systemd[1]: Stopped target Local File Systems (Pre). > systemd[1]: Stopped Create Static Device Nodes in /dev. > 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=? addr=? terminal=? res=success' > systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... > systemd[1]: Stopped Remount Root and Kernel File Systems. > 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=? terminal=? res=success' > lvm[1124]: 3 logical volume(s) in volume group "fedora" unmonitored > systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. > 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=? terminal=? res=success' > juno systemd[1]: Stopping LVM2 metadata daemon... > juno lvmetad[839]: Failed to accept connection errno 11. > systemd[1]: Stopped LVM2 metadata daemon. > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-lvmetad comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > juno systemd-cryptsetup[1099]: Failed to deactivate: Device or resource busy > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c.service: Control process exited, code=exited status=1 > systemd[1]: Stopped Cryptography Setup for luks-862c1862-0497-442f-9442-a7cd6a73b46c. > audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c.service: Unit entered failed state. > systemd[1]: systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c.service: Failed with result 'exit-code'. Looks like cryptsetup cannot close an encrypted partition. Did you try to log out from your X (Gnome?) before the upgrade? Then switch to a tty (can be reached via CTRL-ALT-Fx). From there, as root, two commands: # dnf check-update # dnf upgrade (Sorry, I have no idea about how yum works ... ) Or https://www.happyassassin.net/2016/10/04/x-crash-during-fedora-update-when-system-has-hybrid-graphics-and-systemd-udev-is-in-update/ maybe starting with this line: "If you don’t use GNOME, you can use the offline update system via pkcon, like this:" HTH Wolfgang > systemd[1]: Reached target Unmount All Filesystems. > systemd[1]: Removed slice system-systemd\x2dcryptsetup.slice. > kernel: kauditd_printk_skb: 102 callbacks suppressed > kernel: audit: type=1130 audit(1514917562.780:129): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' > systemd[1]: Reached target Shutdown. > systemd[1]: Reached target Final Step. > systemd[1]: Starting Reboot... > systemd[1]: Shutting down. > systemd[1]: Hardware watchdog 'iTCO_wdt', version 0 > systemd[1]: Set hardware watchdog to 10min. > kernel: watchdog: watchdog0: watchdog did not stop! > systemd-shutdown[1]: Sending SIGTERM to remaining processes... > systemd-journald[821]: Journal stopped > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
