Re: Bug#1035360: bookworm RC2 installation leaves luks encrypted system in unbootable state
Cyril Brulebois <[email protected]>
| Newsgroups | gmane.linux.debian.devel.live,gmane.linux.debian.devel.cd |
|---|---|
| Organization | Debian |
| Message-ID | <[email protected]> |
[ Reordering slightly ] Cyril Brulebois <[email protected]> (2023-05-02): > Paul Seelig <[email protected]> (2023-05-02): > > Attached installation logs should be sufficiently verbose about what > > actually happened underneath. > > Either it was forgotten or dropped by the BTS; please use reply-all, > and attach it compressed (to avoid hitting size limits on either the > BTS side or on the debian-boot ML side). For reference: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035360#10 - https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=1035360;filename=installer-logs.tar.xz;msg=10 > > Apparently, the required cryptsetup-initramfs packages were removed > > from the system during the last instalation stages, rendering the > > resulting system unbootable. That's not quite what happened. Instead, the cryptsetup-initramfs wasn't available to start with: Apr 30 16:11:44 in-target: Package cryptsetup-initramfs is not available, but is referred to by another package. Apr 30 16:11:44 in-target: E: Package 'cryptsetup-initramfs' has no installation candidate Later on, cryptsetup got removed along with a bunch of live packages. Presumably, if cryptsetup-initramfs had been successfully installed, it would have kept cryptsetup around. Again, I'm not familiar with the live environment, it'd be great if some with some knowledge about the way it operates and/or the way it's built could comment on this. Adding debian-live@ for now, but might be debian-cd@ territory… Very wild guess: Could cryptsetup-initramfs be missing from live-setup? https://salsa.debian.org/images-team/live-setup.git Cheers, -- Cyril Brulebois ([email protected]) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmRQRt0ACgkQ/5FK8MKz VSDvAA/8C60OQ51Wu0fUx/7xpuQ6DkieH2DiuRuPo5rSIe7T5P7SLaMmUsbWDYgI 4egYxWqBt16cM1g1UlfFjg/CooEWATjFnktcWFlEhln8p7/Q4AMGk+6fdPxj/fOX wKvVK6oYk9vph46TqIESMNK46a1Wgb5/vHRhv9gZhyNGNPN/dGg4i2BGvPkIsJRS bROcJsxsksVAE3p/NJZmaop+zD+ViVHIhvmYLdQobyoXnb0BNQ0j1rZe17nUGu2V Ycff2RQqLp2NwKSdyZxdFFm1KPn0mlMp6ZdFycIWcmQ+tOES4pcSk2F6x7JOWIus Xjq34Tp13aExZ3TFpaWcSDX6eGLaubaN5Nm7oAPbzEicYKEHiIa49sbHmpfKHpOF FO2r8RvIVFfYWZ7+TMvrzCEVthu4dEdSYCds28JfwA4OMiNtDuWamg438UxgR7Yk wjwIzQegdvYGHvIuaSrrja+mhq3zt0u7K4kB/QzSALRi9D/5rO/RaXBZTunclZGu KiroDxsysWJXR3QTWsmPqY0A/NS6iEzLqQIN6WtBCCDSlLedmWtyaPuHklmaAE0R j1mzjZFOGUOPujeHGiX2kTLKHdUegmbONt766vMuG+Tu+2N4yC9Zp/7fDyhg2r0V 31evVrfjUbHMqUWh1NKXs0O6L5/0lPWK0c7R5RNrIBvkXNqRdJ4= =+q4X -----END PGP SIGNATURE-----