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

[Josh Jones]

It is the root filesystem which is failing to be remounted read-only -
this is a simple setup with only one filesystem for the whole system.

It seems to be happening right at the very very end of the shutdown
sequence - I have attached a picture of the error; quality is poor
because I had to capture it from video footage. Is there any way to
even have anything saved to disk so late in the sequence?

Thanks for your help and attention with this; I'm willing to try
whatever you suggest to help work out what's going on - if that is even
possible..!


Josh


On Sun, 2020-12-06 at 16:08 +0100, Michael Biebl wrote:
> Am 06.12.2020 um 12:45 schrieb Josh Jones:
> > Please see attached debug log from last offline update. It failed
> > to
> > unmount cleanly again. Apologies it took a few days to provide
> > this.
> 
> I don't see a failed unmount attempts in this log unfortunately. Or
> am I 
> missing something?
> Which file system(s) in particular did not unmount cleanly?
> 
> You might also have a look at 
> https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/README.Debian 
> 
> "Debugging boot/shutdown problems"
> to gather logs after journald has been shut down.
> 
> 
> 
> Michael
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: console-976101.png
Type: image/png
Size: 792188 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20201206/9a00a62a/attachment-0001.png>