eliloconfig and cryptsetup issues on -current install with full disk encryption

sebre · 09-01-2019, 06:13 PM

I had two issues installing current on a full disk encrypted (LUKS+LVM) NVME disk.
I usually install -stable on pretty old computers. EFI as well as -current were new things for me. Until now, full disk encryption always worked for me thanks to README_CRYPT.txt.

Here is how I solved the issues.

1 - eliloconfig did not work. The setup installer just skipped it after it telling me not to install lilo.
Solved by manually mounting the EFI partition (/dev/nvme0n1p2 in my case) on /boot/efi (or /mnt/boot/efi if still in setup stage). And running eliloconfig again.

2 - cryptsetup failed on reboot with message "libgcc_s.so.1 must be installed for pthread_cancel to work".
This small patch on /sbin/mkinitrd was enough to make it work, it just adds the missing dynamic lib to initrd.gz :

Code:

@@ -228,6 +228,7 @@
 copy_libs() {
   # First copy the essential glibc files:
   find /lib /lib64 -name "ld-*so*" -o -name "libnss_files*so*" -o -name "libnss_compat*so*" 2> /dev/null | xargs -I'{}' cp -P --parents '{}' $SOURCE_TREE/
+  find /usr/lib64 -name "libgcc_s*sosi cela devrait évoluer*" 2> /dev/null | xargs -I'{}' cp -P --parents '{}' $SOURCE_TREE/
 
   # Then copy all remaining libs our initrd files link against:
   COUNT=1

Someone can probably do better but at least it worked for me. Hope it can help.

Thanks.

enorbet · 09-02-2019, 12:08 PM

Nice. Thank you, sebre.

slackerz · 09-07-2020, 01:47 PM

Interesting find. I recently set up an encrypted root system on a nvme disk but the system wouldn't boot, hanging after the cryptsetup luksOpen stage. It's curious why didn't mkinitrd know about this library in the first place?

I've done a few of setups these over the years and never had to add the library manually. But this time I was using cryptsetup-2 backported to 14.2 instead of cryptsetup-1.7. I wonder if the issue was related.