[pkg-cryptsetup-devel] Bug#939766: cryptsetup-initramfs: Trying to boot linux-image-5.2.0-2-amd64 fails, linux-image-4.19.0-5-amd64 works.
Alexander Brock
Brock.Alexander at web.de
Sun Sep 8 23:53:44 BST 2019
I searched for clues why that libgcc_s.so.1 is not added and found the
script:
/usr/share/initramfs-tools/hooks/cryptroot
it contains the line:
LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')"
but on my machine there is no /bin/libc.so.[0-9.-]+ instead it is in
/usr/lib/x86_64-linux-gnu. Therefore $LIBC_DIR is empty which leads to
the "find: ‘’: No such file or directory" error message in the log
(https://paste.debian.net/1099530/)
Allowing any number of characters before the /lib fixes the problem:
LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* =>
(.*/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')"
I changed this and now the 5.2 kernel boots again. I made a merge
request:
https://salsa.debian.org/cryptsetup-team/cryptsetup/merge_requests/10
More information about the pkg-cryptsetup-devel
mailing list