Bug#1078792: (no subject)

2025-04-19 Thread Patrick Schleizer
Related follow-up issue: Unable to boot LUKS-encrypted system https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103457 Related upstream discussion on hostonly mode versus portability: * https://github.com/dracut-ng/dracut-ng/pull/1238 * https://github.com/dracut-ng/dracut-ng/issues/748

Bug#1078792: the case for generic initrd - "hostonly=no"

2025-04-17 Thread Patrick Schleizer
It is my hopefully reasonable expectations, that a generic initrd (presumably "hostonly=no") does support LUKS encryption. In any case, I very much prefer generic initrd. By "generic initrd", I mean "create once - boot anywhere". Install on internal hard drive, copy to USB, boot on another com

Bug#1078792:

2024-12-11 Thread Gombi
> does not boot with a default dracut installation unless I set "hostonly=yes". This is expected. The details of the LUKS encryption is specific to the host, and hostonly=yes is required to pick up these configurations on your host and make it available in the generated initrd. On Ubuntu ( https:

Bug#1078792: unbootable system after installing dracut on a standard Debian installation - #2

2024-12-09 Thread Celejar
Package: dracut Version: 105-2 Followup-For: Bug #1078792 Hi, I'm *still* seeing this problem, or at least something similar, with version 105-2: My system, set up using the official installer with a LUKS encrypted root partition, which has been working perfectly for years with initramfs-

Bug#1078792: unbootable system after installing dracut on a standard Debian installation - #2

2024-09-27 Thread Aaron Rainbolt
On Fri, Sep 27, 2024 at 3:44 PM Thomas Lange wrote: > I think we do not want to add systemd-cryptsetup as a hard dependency > to one of the dracut packages. What about adding a Recommends: to > dracut-core which already includes a Recommends: for cryptsetup and > systemd? > But systemd already re

Bug#1078792: unbootable system after installing dracut on a standard Debian installation - #2

2024-09-27 Thread Thomas Lange
I think we do not want to add systemd-cryptsetup as a hard dependency to one of the dracut packages. What about adding a Recommends: to dracut-core which already includes a Recommends: for cryptsetup and systemd? But systemd already recommends systemd-cryptsetup so I wonder why you do not have it i

Bug#1078792: unbootable system after installing dracut on a standard Debian installation - #2

2024-09-26 Thread Aaron Rainbolt
The underlying cause of this appears to be a missing dependency. Dracut doesn't include cryptsetup in the initrd if systemd is used within the initrd - in that instance it requires systemd-cryptsetup. systemd-cryptsetup is not installed by default when one installs dracut, leaving the user with no

Bug#1078792: unbootable system after installing dracut on a standard Debian installation - #2

2024-08-19 Thread Jonatas
Package: dracut-install Version: 103-1 Followup-For: Bug #1078792 X-Debbugs-Cc: dkdj3p...@mozmail.com Dear Maintainer, Bug in initramfs "mdadm: No device listed..." (initrd.img-6.10.4-amd64), system boot only in older kernel initrd.img-6.10.3-amd64. *** Reporter, please consider

Bug#1078792: unbootable system after installing dracut on a standard Debian installation - #2

2024-08-16 Thread Patrick Schleizer
Package: dracut Severity: important Exactly the same issue as reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041614 is happening again. Not duplicating here. [1] This is happening because upstream has reverted the prior fix. [2] [1] Why did I not post in the old bug? Because i