[solved] luks/lvm - problem with initramfs

[orinoco]

Hello,

I run into a boot-problem with lvm inside a luks encrypted disk (setup based on Siduction-Wiki). The problem is similar to a bug report on Debian bugtracker.

I've installed latest cryptsetup package

Code Auswählen Erweitern

$ LANG=C apt policy cryptsetup*
cryptsetup-bin:
  Installed: 2:2.0.3-3
  Candidate: 2:2.0.3-3
  Version table:
*** 2:2.0.3-3 500
        500 https://cloudfront.debian.net/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
cryptsetup-initramfs:
  Installed: 2:2.0.3-3
  Candidate: 2:2.0.3-3
  Version table:
*** 2:2.0.3-3 500
        500 https://cloudfront.debian.net/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
cryptsetup-run:
  Installed: 2:2.0.3-3
  Candidate: 2:2.0.3-3
  Version table:
*** 2:2.0.3-3 500
        500 https://cloudfront.debian.net/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
cryptsetup:
  Installed: 2:2.0.3-3
  Candidate: 2:2.0.3-3
  Version table:
*** 2:2.0.3-3 500
        500 https://cloudfront.debian.net/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Creation of initramfs breaks with

Code Auswählen Erweitern

$ sudo update-initramfs -u -k 4.17.2-towo.2-siduction-amd64  update-initramfs: Generating /boot/initrd.img-4.17.2-towo.2-siduction-amd64
cryptsetup: WARNING: No crypttab entry for sda3_crypt
cryptsetup: WARNING: No crypttab entry for sda3_crypt
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'crypsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
I: The initramfs will attempt to resume from /dev/dm-1
I: (UUID=3d82d2c3-ed92-4d6d-8132-44c78bdb2691)
I: Set the RESUME variable to override this.


The recommended uninstallation of cryptsetup-initramfs makes me frightning

Code Auswählen Erweitern

$ LANG=C sudo apt -Vs remove cryptsetup-initramfs
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following package was automatically installed and is no longer required:
   cryptsetup-run (2:2.0.3-3)
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
   cryptsetup (2:2.0.3-3)
   cryptsetup-initramfs (2:2.0.3-3)
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Remv cryptsetup [2:2.0.3-3]
Remv cryptsetup-initramfs [2:2.0.3-3]

Will I be able to unlock my encrypted volumes afterwards?

Fortunately I have a working initramfs for kernel 4.17.1-towo.4-siduction-amd64 at the moment as a fallback. I don't want to destroy it, too.

[Lanzi]

you have checked your crypttab?

No crypttab entry for sda3_crypt

[orinoco]

Hello Lanzi,


really strange. In the past it was not nessessary to add sda3_crypt. Now it's in there and I can create a working initial ramdisk with the latest kernel. Just saw some warnings during boot but it works now. Maybe the time is coming to make a fresh install. All in all thank you for your support.

[bluelupo]

Hi all,

I also have the warnings at startup before entering the LUKS/dm-crypt password. The warnings are only displayed on the latest kernel 4.17.2-towo.2.

As a workaround I stay with the previous kernel for now.

[melmarker]

I also have the warnings at startup before entering the LUKS/dm-crypt password. The warnings are only displayed on the latest kernel 4.17.2-towo.2.

Cool - what about to take some time and read the changelogs - btw. it isn't kernel related. It might be that i'm sound not nice, but not every warning is a kernel warning - and there might be reasons for some developers and package maintainers to print warnings.

https://tracker.debian.org/media/packages/c/cryptsetup/changelog-22.0.3-2

Code Auswählen Erweitern


    + Print a warning inviting the user to uninstall 'cryptsetup-initramfs'
      if 1/ the CRYPTSETUP configuration option is unset or null (the
      default), and 2/ the hook didn't detect any device to be unlocked at
      initramfs stage.  The benefit is two-fold: it guides users through the
      package split, and warns them that their system might not reboot if the
      hook script didn't work properly.