[pkg-cryptsetup-devel] Bug#1140141: cryptsetup: Failure to boot fresh install via cryptroot-unlock with an encrypted home partition

[Alez]

Hmm. As far as the installer goes, having the debian-installer mark the 
device with |x-initrd.attach| which appears to have similar 
functionality (systemd fomat) but not |initramfs| seems like an 
oversight or a bug in itself. The installer should leave the computer in 
a bootable state. I suppose the installer should either also add the 
|initramfs| option, or else the |x-initrd.attach |flag it already adds 
should produce similar behaviour for the purposes of determining drives 
required at initramfs time.


On Tue, 16 Jun 2026 18:14:04 +0200 Guilhem Moulin <guilhem at debian.org> 
wrote:

 > On Tue, 16 Jun 2026 at 10:38:29 -0500, Alez wrote:
 > > The installer should leave the computer in a bootable state.
 >
 > The computer is bootable isn't it? AFAIK remote unlocking isn't done by
 > the installer itself.
 >
 > --
 > Guilhem.
 >
 >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20260616/f4b0341d/attachment.htm>