Arch Linux

ttshaw1

Member

Registered: 2020-04-12

Posts: 47

[Solved] Unable to boot, systemd can't find libcrypto.so.1.1

I've been trying to figure out a regression in my drawing tablet and decided to downgrade linux, linux-headers, libinput, and system-d to the version they were at on November 1st, 2022. I downloaded them from the archive and installed from the local files. Pacman didn't give any warnings about dependencies so I said go for it. (From trying to figure this out, I learned this is bad and I shouldn't do partial downgrades)

Now when I boot I get this error message when trying to decrypt my partition: https://i.imgur.com/24dIX9v.png

My setup:
My disk has 4 partitions. sdb1 is / leftover from an old install, sdb2 is my /boot folder, sdb3 is my /home folder, and sdb4 is /.  fstab doesn't include sdb1 so I figure that shouldn't matter. There's another disk that also shouldn't be involved.
sdb3 and sdb4 are encrypted, following Example 3
Decryption happens at boot. crypttab is set up to require a typed password for both encrypted partitions

But I've booted from an Arch live USB drive, mounted the partitions and chrooted in, updated all my packages, installed openssl-1.1, and regenerated my grub config file. libcrypto.so.1.1 exists in /lib and /usr/lib, and I copied it into the same folders on sdb1 for good measure.

Essentially, I don't understand how systemd can't find libcrypto.so.1.1. It's in what I understand to be the shared library locations, and is part of a package that was installed through pacman without issue. Anyone know what's going on?

Last edited by ttshaw1 (2023-08-31 04:43:30)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: [Solved] Unable to boot, systemd can't find libcrypto.so.1.1

That's happening in your initramfs. You need to rebuild it after installing the old package.

But don't expect everything to work. Arch doesn't work well with a partially updated system.

ttshaw1

Member

Registered: 2020-04-12

Posts: 47

Re: [Solved] Unable to boot, systemd can't find libcrypto.so.1.1

Good call. In this case I had reinstalled the modern packages in arch-chroot but mkinitcpio didn't trigger. Running "mkinitpcio -P" manually worked for one of my two kernels and I'm able to get booted.

For the other kernel, I got an error "'/lib/modules/6.0.6-arch1-1' is not a valid kernel module directory". That version number is the one I'd partially downgraded initially. But I've updated linux and linux-headers to the latest, 6.4.12.arch1-1, so I don't know what's pointing mkinitcpio to that old version. Reinstalling linux and linux-headers in pacman ran mkinitcpio with the correct version number, which solved it. Thanks.