Your message dated Wed, 28 Apr 2021 06:32:15 +0200
with message-id <20210428043215.aeytn4obsv735...@mraw.org>
and subject line Re: Bug#939585: installation-reports: confirmed with current
installer
has caused the Debian Bug report #939585,
regarding installation-reports: Unable to boot from LVM on encrypted volume -
missing cryptsetup in initramfs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
939585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Installation using manually partioned disk by installer containing LVM on
encrypted volume
* What exactly did you do (or not do) that was effective (or
Manually partition drive by installer:
- primary boot partition
- encrypted volume
- LVM on encrypted volume containing root and swap partitions
Continue installation to the end.
An alternative would be trying to encrypt the whole disk. This fails in a more
complete way.
This used to work fine with buster as testing release already.
* What was the outcome of this action?
After reboot and some error messages about missing LVM volumes you will be
dropped to an initramfs shell.
Obviously cryptsetup is missing although installed by d-i with no errors and
there are no errors reported by d-i during generaton of initramfs.
* What outcome did you expect instead?
A working installation where cryptsetup with or without plymouth asking for
passphrase and setting up encrypted volumes.
Cause:
cryptsetup-initramfs is not installed. I was able to fix the situation by
chroot and installing it in the end of the installation.
-- System Information:
Debian Release: bullseye/sid
APT prefers: -
APT policy: -
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.02-generic
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: -
--- End Message ---
--- Begin Message ---
Norbert Preining <norb...@preining.info> (2021-04-27):
> On Fri, 23 Apr 2021, Cyril Brulebois wrote:
> > Please share the installer's syslog (/var/log/installer), preferably
> > compressed due to mail size limits.
>
> Not available anymore, I trashed the whole system.
>
> My guess is - why it worked on second run - is that one has to activate
> LVM otherwise it doesn't work. If you just add an encrypted partition
> it seems that the necessary packages are missing.
Sorry, but you're not reporting anything actionable, so I'll just stick
to my initial assessment: Arne's original problem was fixed a long while
ago:
partman-crypto (106) unstable; urgency=high
* Merge patch by Guilhem Moulin to pull cryptsetup-initramfs instead of
cryptsetup, since the former is now responsible for the cryptsetup
initramfs integration (Closes: #930228).
-- Cyril Brulebois <k...@debian.org> Thu, 28 Nov 2019 10:50:19 +0100
and I'm pretty sure you're not running into this problem. Installing on
encrypted LVM is one of my test scenarios and that works like a charm.
Feel free to open a fresh bug report with details if you run into this
again.
Cheers,
--
Cyril Brulebois (k...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
--- End Message ---
