On Tue, 2026-04-07 at 11:44 +0200, Benjamin Drung wrote: > On Tue, 2026-04-07 at 09:38 +0200, Christian Kastner wrote: > > On 2026-04-06 10:50, Christian Kastner wrote: > > > I can now confirm that it was the dracut 110-8 upload that triggered > > > this new boot failure. Specifically, it was commit bebb2681, which > > > added: > > > > > > fix-dracut-enable-hostonly_cmdline-in-hostonly-mode-again.patch > > > > > > Disabling this patch fixes the issue for me again [...] > > > > So I compared the output of a trixie image build (which continues to > > successfully EFI boot) and an unstable image build (which exhibits the > > problem). > > > > There is one key difference in the image build log when the kernel gets > > installed. Here is a snippet from the unstable build: > > > > Setting up linux-image-6.19.11+deb14-amd64 (6.19.11-1) ... > > I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.19.11+deb14-amd64 > > I: /initrd.img.old is now a symlink to boot/initrd.img-6.19.11+deb14-amd64 > > I: /vmlinuz is now a symlink to boot/vmlinuz-6.19.11+deb14-amd64 > > I: /initrd.img is now a symlink to boot/initrd.img-6.19.11+deb14-amd64 > > /etc/kernel/postinst.d/dracut: > > dracut[W]: Turning off host-only mode: /dev is not mounted! > > ... > > > > The trixie build lacks this dracut warning. > > > > So it would appear that in image builds, this problem stems from > > host-only mode previously being on, and now being turned off. > > Those two reports gave me a clue. I assume the opposite. You want > hostonly disabled. The patch fix-dracut-enable-hostonly_cmdline-in- > hostonly-mode-again.patch enables hostonly-cmdline by default again, but > this: > > dracut[W]: Turning off host-only mode: /dev is not mounted! > > does not turn off hostonly-cmdline which causes the host config to leak > into the initrd. I'll prepare a fix for dracut.
Here comes the fix: https://github.com/dracut-ng/dracut-ng/pull/2351 Can you test that this fix solves your issue? -- Benjamin Drung Debian & Ubuntu Developer
