Control: reassign -1 fwupd
Control: retitle -1 fwupdtool keeps / fs busy on shutdown/reboot
Am 08.12.20 um 21:05 schrieb Michael Biebl:
Am 08.12.20 um 20:39 schrieb Josh Jones:
Amazing, that has taught me something very useful!
shutdown-log.txt attached and error is visible!
Thanks.
So
Am 08.12.20 um 20:39 schrieb Josh Jones:
Amazing, that has taught me something very useful!
shutdown-log.txt attached and error is visible!
Thanks.
So from a quick glance it seems fwupd keeps your / busy and prevents it
from being remounted ro.
Amazing, that has taught me something very useful!
shutdown-log.txt attached and error is visible!
Josh
On Sun, 2020-12-06 at 21:36 +0100, Michael Biebl wrote:
> Am Sonntag, den 06.12.2020, 19:28 +0100 schrieb Michael Biebl:
> > Am 06.12.20 um 17:04 schrieb Josh Jones:
> > > It is the root
Am Sonntag, den 06.12.2020, 19:28 +0100 schrieb Michael Biebl:
> Am 06.12.20 um 17:04 schrieb 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
Am 06.12.20 um 17:04 schrieb 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
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
No worries - I will send you the debug journal at the next package update - or
if I have time tomorrow I will try to install outdated versions of the packages
last updated to force it to happen. Whatever is happening is pretty consistent
for me by the looks of it.
I have just enabled
Control: tags -1 unreproducible
Am 01.12.20 um 18:02 schrieb Josh Jones:
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)
So, I tried this in a test VM.
The offline update
Am 01.12.20 um 18:02 schrieb Josh Jones:
Sorry which log do you mean by debug journal log? Apologies for my
ignorance.
Enable persistent journal (see
/usr/share/doc/systemd/README.Debian.gz)
When booting into the offline based upgrade, add
"systemd.log_level=debug" to the kernel command
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:
>
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
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
12 matches
Mail list logo
