@Nick: You asked for logs and reproduction details. Here's the complete evidence package.
Attached: bug-2141741-evidence.zip The zip contains: - dpkg timeline showing 3-day failure pattern - DKMS error logs (VirtualBox exit 11) - The buggy script (exit 0 at line 26) - System config proving NVMe needs initrd - README with complete failure chain Key point: Yes, DKMS should fail harder (that's Bug #2136499). But 55-initrd.install should ALSO fail when it detects missing initrd. That's defense in depth. The script already detects the problem (line 23 check works). It just returns the wrong exit code (line 26: exit 0 instead of exit 1). All details are in the zip. ** Attachment added: "Complete evidence package with logs and reproduction" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2141741/+attachment/5948262/+files/bug-2141741-evidence.zip -- 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/systemd/+bug/2141741/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
