@michel.ekimia
Until Ubuntu packages address this officially, here is how you can
protect your client machines from bricking on reboot:
1. Identify and fix any machines that already have a kernel installed
without an initrd:
for k in /boot/vmlinuz-*; do
v="${k#/boot/vmlinuz-}";
if [ ! -f "/boot/initrd.img-$v" ]; then
echo "Missing initrd for $v, generating now...";
sudo update-initramfs -c -k "$v";
fi;
done
sudo update-grub
2. If you have an outdated DKMS package that keeps breaking kernel
installations across the fleet:
The standard way to stop DKMS from blocking kernel updates is: sudo touch
/etc/dkms/no-autoinstall
This disables automatic DKMS module builds during kernel installs. The
outdated third-party driver will not be built, but initramfs-tools will
complete normally, creating a valid initrd.img so the machine boots
safely on NVMe. Once the vendor provides an updated DKMS driver
compatible with the new kernel, you can remove that file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2141741
Title:
55-initrd.install silently exits 0 when initrd missing causing
undetectable kernel panic on NVMe systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2141741/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
