Bug#976101: systemd: Offline update installation in systemd (via gnome-update) doesn't cleanly unmount filesystem

Josh Jones josh at joshbox.org
Tue Dec 1 17:02:35 GMT 2020


Sorry which log do you mean by debug journal log? Apologies for my
ignorance.

(Incidentally this problem has occured on two out of three offline
updates in recent days)

On Sun, 2020-11-29 at 19:45 +0100, Michael Biebl wrote:
> Control: tags -1 + moreinfo
> 
> Am 29.11.20 um 19:23 schrieb Josh:
> > Package: systemd
> > Version: 241-7~deb10u4
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > On two recent clean installations of Buster, I am noticing that
> > choosing to
> > install package updates through gnome-software, and therefore the
> > systemd
> > offline update system, results in the root filesystem not being
> > unmounted
> > properly once packages are installed and therefore gives an fsck
> > error on
> > reboot:
> > 
> > Failed to remount '/' read-only; Device or resource busy
> > 
> > Followed by journal recovery on reboot.
> > 
> > I haven't noticed any serious problems subsequently but it seems
> > like asking
> > for trouble for the filesystem to not be cleanly unmounted right
> > after packages
> > are updated. I have seen this on two machines, neither using 3rd
> > party repos
> > etc.
> 
> Can you please provide a (debug) journal log from such an offline
> update.
> 
> Michael



More information about the Pkg-systemd-maintainers mailing list