Ubuntu 20.04.3 LTS on an Intel NUC11 Enthusiast Mini PC - NUC11PHKi7CAA
(Has an Nvidia GPU)
Rebooted today after applying latest software updates, and it no longer boots.
GRUB loads fine, but system freezes with a black screen after GRUB
Research and Troubleshooting:
Selecting "Advanced boot options" I see choices for two kernels and their associated "Recovery Mode" options:
- 5.11.0-43
- 5.11.0-43 (recovery mode)
- 5.11.0-41
- 5.11.0-41 (recovery mode)
None of these 4 work. If I select the recovery mode option for either kernel, I can see that the system is freezing after "Loading initial ramdisk"
Installed latest BIOS (PGTGL579.0065, Released Oct 14, 2021), but it didn't help.
I was able to boot a Ubuntu live CD and unlock all of the encrypted volumes manually.
I ran the Boot Repair Disk Utility, the output of which is here: https://paste.ubuntu.com/p/JrkYFSMSn7/
I successfully chrooted to the root partition of my system's root partition on the internal SSD and ran apt update and apt upgrade successfully, but no new updates were available.
/var/log/dmesg shows a successful boot on 2021-12-19 w/ kernel 5.11.0.43-generic
/var/log/dmesg.0 shows a successful boot on 2021-11-30 w/ kernel 5.11.0.41-generic
Looking at the partition containing the initrd images, I see that both the .43 and .41 versions of the initrd image were modified on 2021-12-23 14:42:05 PM UTC
I rebuilt the ramdisk on the mounted, chrooted boot partition:
update-initramfs -u -v -k 5.11.0-43-generic
And then rebooted. But no luck. What else should I try?
Edit:
I see that the following packages were updated on 2021-12-23 14:41:21:
- netplan.io:amd64 (0.103-0ubuntu5~20.04.3, 0.103-0ubuntu5~20.04.5),
- gnome-shell-extension-desktop-icons:amd64 (20.04.0-3~ubuntu20.04.5, 20.04.0-3~ubuntu20.04.6),
- python3-software-properties:amd64 (0.98.9.5, 0.99.9.8),
- openssl:amd64 (1.1.1f-1ubuntu2.9, 1.1.1f-1ubuntu2.10),
- update-notifier-common:amd64 (3.192.30.9, 3.192.30.10),
- libfprint-2-2:amd64 (1:1.90.2+tod1-0ubuntu1~20.04.4, 1:1.90.2+tod1-0ubuntu1~20.04.5),
- libpulsedsp:amd64 (1:13.99.1-1ubuntu3.12, 1:13.99.1-1ubuntu3.13),
- pulseaudio:amd64 (1:13.99.1-1ubuntu3.12, 1:13.99.1-1ubuntu3.13),
- ubuntu-advantage-tools:amd64 (27.4.1~20.04.1, 27.4.2~20.04.1),
- google-chrome-stable:amd64 (96.0.4664.93-1, 96.0.4664.110-1),
- software-properties-gtk:amd64 (0.98.9.5, 0.99.9.8),
- libfprint-2-tod1:amd64 (1:1.90.2+tod1-0ubuntu1~20.04.4, 1:1.90.2+tod1-0ubuntu1~20.04.5),
libpulse0:amd64 (1:13.99.1-1ubuntu3.12, 1:13.99.1-1ubuntu3.13),
- libpulse-mainloop-glib0:amd64 (1:13.99.1-1ubuntu3.12, 1:13.99.1-1ubuntu3.13),
- libmm-glib0:amd64 (1.16.6-2~20.04, 1.16.6-2~20.04.1),
- libnetplan0:amd64 (0.103-0ubuntu5~20.04.3, 0.103-0ubuntu5~20.04.5),
- pulseaudio-module-bluetooth:amd64 (1:13.99.1-1ubuntu3.12, 1:13.99.1-1ubuntu3.13),
- modemmanager:amd64 (1.16.6-2~20.04, 1.16.6-2~20.04.1),
- linux-firmware:amd64 (1.187.20, 1.187.23),
- libssl1.1:amd64 (1.1.1f-1ubuntu2.9, 1.1.1f-1ubuntu2.10),
- pulseaudio-utils:amd64 (1:13.99.1-1ubuntu3.12, 1:13.99.1-1ubuntu3.13),
- update-notifier:amd64 (3.192.30.9, 3.192.30.10),
- software-properties-common:amd64 (0.98.9.5, 0.99.9.8)
I assume that one of these updates triggered the rebuild of the initrd image, but am not sure which, or what to do about it.