Re: Device or resource busy when trying to do a software update

[Martin Wagner]

On Fri, 2018-01-05 at 15:54 +0100, Wolfgang Pfeiffer wrote:
> Closed bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1359352
> as  it is said to be a duplicate of
> https://bugzilla.redhat.com/show_bug.cgi?id=1385432
> 
> On this latter page is a hint that the issue might be an LVM one,
> i.e. LVM created during automatic partitioning at install time. Not
> clear ...
> 
> Comment 143
> "I then reinstalled without LVM using custom partioning, updated and
>  now the problem is gone"
> https://bugzilla.redhat.com/show_bug.cgi?id=1385432#c143
> 
> Seems to be serious, and an old bug, and unfixed.
> 

Thanks for the links.

A followup, today I did a Gnome Software restart & upgrade routine and
it worked! Must have been some previous software update (using dnf)
that fixed the issue, because I can't think of anything else that I've
done to fix it. 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Device or resource busy when trying to do a software update

[Wolfgang Pfeiffer]

On Thu, 04 Jan 2018 21:09:05 +0100
Martin Wagner  wrote:

> On Thu, 2018-01-04 at 13:06 +0100, Wolfgang Pfeiffer wrote:
> > Ah, I see: I missed that in your first message - sorry. But if dnf
> > upgrades work, your concerns about not being not be able to upgrade
> > to
> > the next major version of Fedora might be not necessary: there's some
> > upgrade version for dnf that worked for me upgrading from F24 -> F25  
> > ->F26. I've used this Fedora HowTo:  
> > 
> > https://fedoraproject.org/wiki/DNF_system_upgrade  
> 
> I borrowed a good camera from a friend and managed to actually capture
> the messages that the system writes when I try to do a Gnome Software
> restart & update routine. Right after it writes 'Installing updates;
> this could take a while...' it writes 
> 
> Command failed
> Kernel not configured for semaphores (System V IPC). Not using udev
> synchronization code.
> Device-mapper: remove ioctl on fedora-root failed: Device or resourcebusy 

Closed bug
https://bugzilla.redhat.com/show_bug.cgi?id=1359352
as  it is said to be a duplicate of
https://bugzilla.redhat.com/show_bug.cgi?id=1385432

On this latter page is a hint that the issue might be an LVM one,
i.e. LVM created during automatic partitioning at install time. Not
clear ...

Comment 143
"I then reinstalled without LVM using custom partioning, updated and
 now the problem is gone"
https://bugzilla.redhat.com/show_bug.cgi?id=1385432#c143

Seems to be serious, and an old bug, and unfixed.

Good luck!
Wolfgang
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Device or resource busy when trying to do a software update

[Martin Wagner]

On Thu, 2018-01-04 at 13:06 +0100, Wolfgang Pfeiffer wrote:
> Ah, I see: I missed that in your first message - sorry. But if dnf
> upgrades work, your concerns about not being not be able to upgrade
> to
> the next major version of Fedora might be not necessary: there's some
> upgrade version for dnf that worked for me upgrading from F24 -> F25
> ->F26. I've used this Fedora HowTo:
> 
> https://fedoraproject.org/wiki/DNF_system_upgrade

I borrowed a good camera from a friend and managed to actually capture
the messages that the system writes when I try to do a Gnome Software
restart & update routine. Right after it writes 'Installing updates;
this could take a while...' it writes 

Command failed
Kernel not configured for semaphores (System V IPC). Not using udev
synchronization code.
Device-mapper: remove ioctl on fedora-root failed: Device or resourcebusy 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Device or resource busy when trying to do a software update

[Wolfgang Pfeiffer]

On Wed, 03 Jan 2018 20:11:29 +0100
Martin Wagner  wrote:

> On Wed, 2018-01-03 at 18:45 +0100, Wolfgang Pfeiffer wrote:
> > On Tue, 02 Jan 2018 20:06:24 +0100
> > Martin Wagner  wrote:

  [ ... ]

> > 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  
> 
> Yes, that works fine, but that didn't involve any kind of restart like
> the Gnome Software update routine does.

Ah, I see: I missed that in your first message - sorry. But if dnf
upgrades work, your concerns about not being not be able to upgrade to
the next major version of Fedora might be not necessary: there's some
upgrade version for dnf that worked for me upgrading from F24 -> F25
->F26. I've used this Fedora HowTo:

https://fedoraproject.org/wiki/DNF_system_upgrade

Excerpt:
"DNF system upgrade can upgrade your system to a newer release of
Fedora, using a mechanism similar to that used for offline package
updates. The updated packages are downloaded while the system is
running normally, then the system reboots to a special environment
(implemented as a systemd target) to install them. Once installation of
the updated packages is complete, the system reboots again to the new
Fedora release."

Additionally to the recommendations above I recommend doing this
from a VT / TTY - after logging out of X. On the tty I even started the
upgrade from inside a tmux session. Not being sure if this latter
approach is really necessary 

HTH
Wolfgang
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Device or resource busy when trying to do a software update

[Martin Wagner]

On Wed, 2018-01-03 at 18:45 +0100, Wolfgang Pfeiffer wrote:
> On Tue, 02 Jan 2018 20:06:24 +0100
> Martin Wagner  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 ...
> 

I've used 'yum update' to update the system because the Gnome Software
update routine didn't work any more


> 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

Yes, that works fine, but that didn't involve any kind of restart like
the Gnome Software update routine does.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Device or resource busy when trying to do a software update

[Wolfgang Pfeiffer]

On Tue, 02 Jan 2018 20:06:24 +0100
Martin Wagner  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 
> 

Re: Device or resource busy when trying to do a software update

[Terry Polzin]

OK just a thought.

On Tue, Jan 2, 2018 at 2:23 PM, Martin Wagner 
wrote:

> On Tue, 2018-01-02 at 14:12 -0500, Terry Polzin wrote:
> > Any NFS or CIFS mounts active?
> >
>
> Yes, but it doesn't make any difference even if I manually umount the
> nfs shares before trying to do a software update.
>
>
> > On Tue, Jan 2, 2018 at 2:06 PM, Martin Wagner
> > 
> > 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 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'.
> > > 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\x2d94
> > > 42\x2da7cd6a73b46c
> > > 

Re: Device or resource busy when trying to do a software update

[Martin Wagner]

On Tue, 2018-01-02 at 14:12 -0500, Terry Polzin wrote:
> Any NFS or CIFS mounts active?
> 

Yes, but it doesn't make any difference even if I manually umount the
nfs shares before trying to do a software update. 


> On Tue, Jan 2, 2018 at 2:06 PM, Martin Wagner
> 
> 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 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'.
> > 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\x2d94
> > 42\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
> > 

Re: Device or resource busy when trying to do a software update

[Terry Polzin]

Any NFS or CIFS mounts active?

On Tue, Jan 2, 2018 at 2:06 PM, Martin Wagner 
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 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'.
> 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@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list --