Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot
I can confirm this bug. After doing an apt full-upgrade, I faced the
same issue as OP. However, I was not able to fix it by downgrading
packages, but instead used a similar approach to the way described in
the btrfs bug #950556 [1].
After chrooting into the system, I changed the following file:
$ diff /usr/share/initramfs-tools/hooks/cryptroot.backup
/usr/share/initramfs-tools/hooks/cryptroot
416c416
< find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while
read so; do
---
> find -L "/lib" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do
After this, I updated initramfs with "update-initramfs -u -k all".
Note: for this to work cleanly, you need to bind proc, dev etc. and you
need to open your encrypted volume with the same name as described in
your system's /etc/crypttab. The commands I used:
sudo cryptsetup open /dev/sda5 sda5_crypt
[...]
sudo mount --bind /dev /mnt/dev
[...]
Cheers
Nico
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950556
Reply to: