I believe I just observed the same issue again, and now have a log from that
See below.
I've also come accross a simular issue here
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1699520
"plymouth --ping" is also hanging for me, I will attach a strace
First the log which happoned as I used `apt` to install an other unrelated tool
$ sudo apt install net-tools
[sudo] password for skk:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
gyp javascript-common libc-ares2 libfprint-2-tod1 libjs-inherits
libjs-is-typedarray libjs-psl libjs-typedarray-to-buffer libllvm9 libnode-dev
libnode64 libpython2-stdlib libpython2.7-minimal libpython2.7-stdlib libssl-dev
libuv1-dev nodejs-doc python-pkg-resources
python2 python2-minimal python2.7 python2.7-minimal
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
net-tools
0 upgraded, 1 newly installed, 0 to remove and 16 not upgraded.
6 not fully installed or removed.
Need to get 196 kB of archives.
After this operation, 864 kB of additional disk space will be used.
Get:1 http://dk.archive.ubuntu.com/ubuntu focal/main amd64 net-tools amd64
1.60+git20180626.aebd88e-1ubuntu1 [196 kB]
Fetched 196 kB in 0s (938 kB/s)
Selecting previously unselected package net-tools.
(Reading database ... 174869 files and directories currently installed.)
Preparing to unpack .../net-tools_1.60+git20180626.aebd88e-1ubuntu1_amd64.deb
...
Unpacking net-tools (1.60+git20180626.aebd88e-1ubuntu1) ...
Setting up net-tools (1.60+git20180626.aebd88e-1ubuntu1) ...
Setting up grub-common (2.04-1ubuntu26.3) ...
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
Job for grub-common.service failed because a timeout was exceeded.
See "systemctl status grub-common.service" and "journalctl -xe" for details.
invoke-rc.d: initscript grub-common, action "restart" failed.
● grub-common.service - LSB: Record successful boot for GRUB
Loaded: loaded (/etc/init.d/grub-common; generated)
Active: failed (Result: timeout) since Wed 2020-09-09 08:32:40 CEST; 5ms
ago
Docs: man:systemd-sysv-generator(8)
Process: 1985200 ExecStart=/etc/init.d/grub-common start (code=killed,
signal=TERM)
Tasks: 6 (limit: 23958)
Memory: 4.0M
CGroup: /system.slice/grub-common.service
├─ 421180 plymouth --ping
├─ 423955 plymouth --ping
├─ 434262 plymouth --ping
├─ 89 plymouth --ping
├─1923087 plymouth --ping
└─1985208 plymouth --ping
Sep 09 08:27:40 PC-5928-Linux-VM systemd[1]: Starting LSB: Record successful
boot for GRUB...
Sep 09 08:32:40 PC-5928-Linux-VM systemd[1]: grub-common.service: start
operation timed out. Terminating.
Sep 09 08:32:40 PC-5928-Linux-VM systemd[1]: grub-common.service: Failed with
result 'timeout'.
Sep 09 08:32:40 PC-5928-Linux-VM systemd[1]: Failed to start LSB: Record
successful boot for GRUB.
dpkg: error processing package grub-common (--configure):
installed grub-common package post-installation script subprocess returned
error exit status 1
dpkg: dependency problems prevent configuration of grub-efi-amd64-bin:
grub-efi-amd64-bin depends on grub-common (= 2.04-1ubuntu26.3); however:
Package grub-common is not configured yet.
dpkg: error processing package grub-efi-amd64-bin (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of grub-efi-amd64-signed:
grub-efi-amd64-signed depends on grub-efi-amd64-bin (= 2.04-1ubuntu26.3);
however:
Package grub-efi-amd64-bin is not configured yet.
dpkg: error processing package grub-efi-amd64-signed (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of grub2-common:
grub2-common depends on grub-common (= 2.04-1ubuntu26.3); however:
Package grub-common is not configured yet.
dpkg: error processing package grub2-common (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuratiNo apport report written because
the error message indicates its a followup error from a previous failure.
No
apport report written because the error message indicates its a followup error
from a previous failure.
No apport repor
t written because MaxReports is reached already
No apport report written because
MaxReports is reached already
