[dm-crypt] problem with cryptsetup 2.21 - compiled OK but now getting version error

[dm-crypt] problem with cryptsetup 2.21 - compiled OK but now getting version error

[John Williamson]

[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]

I have used dmcrypt and cryptsetup for about 15years on desktops and
thinkpad laptops without too much trouble as long as I spent time going
through the online guides. I am replacing my Thinkpad X301 which had a
128gb ssd but was upgraded to a samsung ssd evo 500 and on both these
drives cryptsetup worked perfectly to encrypt the drive.

I now have a Thinkpad X1 carbon with a 1Tb drive which has an IBM
SSDPEKKF010T8L. I have installed Mint 19.2 running kernel 4.15
providing cryptsetup 2.0.2. When using this to try and create a Luks
header, the operation fails with the message that there is no logical
drive and code 4. having puzzled over this for some time, I realise
that there is a newer version of cryptsetup. Newer versions of the
kernel beyond 5.0 disable the trackpad and do not provide a new version
of cryptsetup so I am now on kernel 4.18 and have managed to
successfully compile cryptsetup 2.21 and remove the binary versions
provided by MINT, however now if I check the version I get the
following error message

"sudo cryptsetup --version"

cryptsetup: relocation error: cryptsetup: symbol
crypt_get_pbkdf_default version CRYPSETUP_2.0 not defined in file
libcryptsetup.so.12 with link time reference


Googling this provides little help so I have decided it is time to ask
for help.

thanks in advance


[-- Attachment #2: system info.txt --]
[-- Type: text/plain, Size: 3936 bytes --]

Host: carbonite1 Kernel: 4.18.0-25-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 
           Desktop: Cinnamon 4.2.4 wm: muffin dm: LightDM Distro: Linux Mint 19.2 Tina 
           base: Ubuntu 18.04 bionic 
Machine:   Type: Laptop System: LENOVO product: 20QDCTO1WW v: ThinkPad X1 Carbon 7th 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: LENOVO model: 20QDCTO1WW v: SDK0J40709 WIN serial: <filter> UEFI: LENOVO 
           v: N2HET35W (1.18 ) date: 08/20/2019 
Battery:   ID-1: BAT0 charge: 51.0 Wh condition: 51.0/51.0 Wh (100%) volts: 17.4/15.4 
           model: LGC 02DL004 serial: <filter> status: Full 
CPU:       Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP arch: Kaby Lake 
           rev: C L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31872 
           Speed: 4100 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 4100 2: 4098 3: 4101 
           4: 4082 5: 4097 6: 4103 7: 4121 8: 4100 
Graphics:  Device-1: Intel vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:3ea0 
           Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa 
           resolution: 2560x1440~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.0.8 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:9dc8 
           Sound Server: ALSA v: k4.18.0-25-generic 
Network:   Device-1: Intel driver: iwlwifi v: kernel port: 2000 bus ID: 00:14.3 chip ID: 8086:9df0 
           IF: wlp0s20f3 state: up mac: <filter> 
           Device-2: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: 3.2.6-k port: efa0 
           bus ID: 00:1f.6 chip ID: 8086:15be 
           IF: enp0s31f6 state: down mac: <filter> 
Drives:    Local Storage: total: 953.87 GiB used: 19.07 GiB (2.0%) 
           ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKKF010T8L size: 953.87 GiB 
           speed: 31.6 Gb/s lanes: 4 serial: <filter> 
Partition: ID-1: / size: 45.58 GiB used: 19.03 GiB (41.8%) fs: ext4 dev: /dev/nvme0n1p5 
Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 2676 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http: //mirror.xnet.co.nz/pub/linuxmint/packages tina main upstream import backport
           2: deb http: //ubuntu.mirrors.theom.nz bionic main restricted universe multiverse
           3: deb http: //ubuntu.mirrors.theom.nz bionic-updates main restricted universe multiverse
           4: deb http: //ubuntu.mirrors.theom.nz bionic-backports main restricted universe multiverse
           5: deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           6: deb http: //archive.canonical.com/ubuntu/ bionic partner
           Active apt repos in: /etc/apt/sources.list.d/official-source-repositories.list 
           1: deb-src http: //mirror.xnet.co.nz/pub/linuxmint/packages tina main upstream import backport
           2: deb-src http: //ubuntu.mirrors.theom.nz bionic main restricted universe multiverse
           3: deb-src http: //ubuntu.mirrors.theom.nz bionic-updates main restricted universe multiverse
           4: deb-src http: //ubuntu.mirrors.theom.nz bionic-backports main restricted universe multiverse
           5: deb-src http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           6: deb-src http: //archive.canonical.com/ubuntu/ bionic partner
Info:      Processes: 248 Uptime: 5h 39m Memory: 15.41 GiB used: 1.24 GiB (8.1%) Init: systemd 
           v: 237 runlevel: 5 Compilers: gcc: 7.4.0 alt: 7 Client: Unknown python3.6 client 
           inxi: 3.0.32 

Re: [dm-crypt] problem with cryptsetup 2.21 - compiled OK but now getting version error

[Milan Broz]

On 28/09/2019 05:41, John Williamson wrote:
> I have used dmcrypt and cryptsetup for about 15years on desktops and
> thinkpad laptops without too much trouble as long as I spent time going
> through the online guides. I am replacing my Thinkpad X301 which had a
> 128gb ssd but was upgraded to a samsung ssd evo 500 and on both these
> drives cryptsetup worked perfectly to encrypt the drive.
> 
> I now have a Thinkpad X1 carbon with a 1Tb drive which has an IBM
> SSDPEKKF010T8L. I have installed Mint 19.2 running kernel 4.15
> providing cryptsetup 2.0.2. When using this to try and create a Luks
> header, the operation fails with the message that there is no logical
> drive and code 4. having puzzled over this for some time, I realise
> that there is a newer version of cryptsetup. Newer versions of the
> kernel beyond 5.0 disable the trackpad and do not provide a new version
> of cryptsetup so I am now on kernel 4.18 and have managed to
> successfully compile cryptsetup 2.21 and remove the binary versions
> provided by MINT, however now if I check the version I get the
> following error message
> 
> "sudo cryptsetup --version"
> 
> cryptsetup: relocation error: cryptsetup: symbol
> crypt_get_pbkdf_default version CRYPSETUP_2.0 not defined in file
> libcryptsetup.so.12 with link time reference

You have apparently old libcryptsetup.so file in the lib path.

Check with ldd over your cryptsetup binary (absolute link will appear there),
and remove it. 

You should use distro packaged version though, that version should take
care about proper library update.

If you compile it yourself, either remove packaged version
before installing your own or be sure you setup the same library paths
(so the new library overwrites the old).

Milan