[SOLVED] Libcrypt.so.3 cannot open and a further problem

F178 · 2022-11-10 14:28:58

Hey all,

like others, I’ve had an error on boot saying

systemd-tmpfiles: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory
/usr/lib/systemd/systemd-udevd: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: no such file or directory

I then followed this thread: https://bbs.archlinux.org/viewtopic.php?id=280992

And I removed Dell-command-configure and rebooted

But it seems I should’ve also rebuilt my initramfs because now I got

Error: device /dev/mapper/volgroup0-lv_root not found. Skipping fsck 
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.

So, I tried to rebuild. I first reinstalled the Linux package because I didn’t seem to have anything in my /boot/ directory. Then I ran mkinitcpio -P but afterwards the problem persists.

Based on the other thread, I also reinstalled libsystemd and openssl and ran ldconfig in case that’s relevant.

For what it’s worth, I’d really appreciate any help. I am quite desperate at this point and really need access to this machine.

Last edited by F178 (2022-11-10 18:15:09)

d.ALT · 2022-11-10 14:44:22

F178 wrote:

Then I ran mkinitcpio -P but afterwards the problem persists.

Any strange outputs? Please post here:

# mkinitcpio -Pv

seth · 2022-11-10 14:45:04

libcrypto.so.3: cannot open shared object file

pacman -Qs openssl
pacman -Qikk openssl

F178 · 2022-11-10 15:12:31

Any strange outputs? Please post here:

I’m on mobile so that is difficult. Maybe the regular output from mkinitcpio helps already? It throws two errors and a couple of warnings

Building image from preset: /etc/mkinitcpio.d/linux-Its.preset:'default'
-> -k /boot/vmlinuz-linux-Its -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-Its. img
==> ERROR: specified kernel image does not exist:
`/boot/vmlinuz-linux-lts'
==› Building image from preset: /etc/mkinitcpio.d/linux-Its.preset: 'fallback'
 -k /boot/vmlinuz-linux-Its -c retc/mkinitcpio.conf -g /boot/initramfs-linux-Its-fallback. img -S autodetect ==> ERROR: specified kernel image does not exist:
`/boot/vmlinuz-linux-Its'
==› Building image from preset: /etc/mkinitcpio.d/linux.preset:
"default'
 -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==› Starting build: 6.0.7-arch1-1
-> Running build hook: [base]
-> Running build hook: [udev]
Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: gat_4xxx
-> Running build hook: [lvm2]
- Running build hook: [filesystems]
Running build hook: [keyboard]
Running build hook: [fsck]
==> Generating module dependencies
==› Creating zstd-compressed initcpio image: /boot/initramfs-linux. img ==› Image generation successful
==› Building image from preset: /etc/mkinitcpio.d/linux.preset:
"fallback'
-k /boot/umlinuz-linux -c /etc/mkinitcpio.conf
==) Starting build: 6.0.7-arch1-1
-g /boot/initramfs-linux-fallback. img -S autodetect
- Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x 
==› WARNING: Possibly missing firmware for module: gla2xxx 
==> WARNING: Possibly missing firmware for module: qed 
==> WARNING: Possibly missing firmware for module: bfa 
==› WARNING: Possibly missing firmware for module: aic94xx 
==> WARNING: Possibly missing firmuare for module: qla1280 
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
Running build hook: [lvm2]
Running build hook: [filesystems]
- Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zst-compressed initcpio image: /boot/initramfs-linux-fallback. img ==› Image generation successful

pacman -Qs openssl
pacman -Qikk openssl

These yield:

 pacman -Qs openssl local/11632-openssl 1:3.0.7-1
The Open Source toolkit for Secure Sockets Layer and Transport Layer Security (32-bit)
local/ libevent 2.1.12-4
Event notification library local/openssl 3.0.7-2
The Open Source toolkit for Secure Sockets Layer and Transport Layer Security 
local/perl-net-ssleay 1.92-2
Perl bindings for OpenSSL and LibreSSL local/pkcs11-helper 1.29.0-2
A library that simplifies the interaction with PKCS11 providers for end-user applications using a simple API and optional OpenSSL engine local/python-pyopenss1 22.1.0-1
Python3 wrapper module around the OpenSSL library local/xmIsec 1.2.36-2
XML Security Library is a C library based on LibXML2
'[root@archiso/]# pacman -Qikk openssl
Name
openssl 
Version: 3.0.2-2
Description: The Open Source toolkit for Secure Sockets Layer and Transport Layer Security
Architecture: ×86_64
URL: https://www.openssl.org
Licenses:. Apache
Groups: None
Provides: libcrypto.so=3-64 libss1.so=3-64
Depends On: glibc
Optional Deps ca-certificates [installed]
perl [installed
Required By :coreutils cryptsetup,
curl git gst-plugins-bad kmod ldns
11632-openss] libarchive libevent libsas1 libshout libssh libssi
perl-net-ssleay pkes11-helper podofo postgresq1-libs ppp python rsync sane scribus
Optional For
socat srt sudo systemd tepdump
tpm2-
None
Conflicts With
None
Replaces
openss1-perl openss1-doc
Installed Size
10.69 MiB
Packager
Pierre Schmitz <pierre@archlinux.de>
Build Date
Tue Nov 1 14:21:33 2022
Install Date
Thu Nov 10 08:36:17 2022
Install Reason
Installed as a dependency for another package
• Install Script
• No
•Validated By
: Signature
openss1: 5688 total files, 0 altered files

(Apologies for the formatting, I’m copying the outputs from photos with text recognition)

seth · 2022-11-10 15:22:03

The errors are because you've the presets for the LTS kernel around, but not the kernel.
The warnings are harmless.

The openssl package versions are all over the place, likely because of the OCR - just make sure it's 3.0.7-2
But there're no errors, so the "libcrypto.so.3: cannot open shared object file" was somehow™ fixed.

Which kernel are you trying to boot and did you maybe forget to mount the boot partition?

d.ALT · 2022-11-10 15:23:47

F178 wrote:

'[root@archiso/]# pacman -Qikk openssl

What are the steps you're following in chroot? Are you inside chroot, aren't you?

F178 · 2022-11-10 15:31:03

Which kernel are you trying to boot and did you maybe forget to mount the boot partition?

I’m trying to boot the regular, non-lts kernel. So 6.0.7.

What do I have to mount the boot partition for? Do I have to do that to remake the initramfs? This might be embarrassing but I did not mount a boot partition at any point…

d.ALT · 2022-11-10 15:37:29

F178 wrote:

I did not mount a boot partition at any point…

Well... Kernel is on boot... Usually... If boot has its own partition, you'll have to mount it, yes! Make sure to be inside chroot!

Last edited by d.ALT (2022-11-10 15:38:02)

seth · 2022-11-10 15:39:59

lsblk -f

And from the chroot look at

journalctl -b -1

The kernel commandline will tell you whether you're booting from the root or boot partition (look whether the location of the kernel contains "/boot" - if not, you're booting from a boot partition)

F178 · 2022-11-10 15:41:41

d.ALT wrote:

F178 wrote:
'[root@archiso/]# pacman -Qikk openssl
What are the steps you're following in chroot? Are you inside chroot, aren't you?

In case that helps, here’s exactly what I’m doing after booting the install medium:

# cryptsetup open /dev/nvme0n1p3 archfilesys
(enter the password for encrypted drive)
# lvchange -ay volgroup0
# mount /dev/volgroup0/lv_root /mnt 
# arch-chroot /mnt
[root@archiso /] # mkinitcpio -P

Or replace the last command with the pacman command I use to show the package output.

F178 · 2022-11-10 15:56:37

seth wrote:

lsblk -f

seth wrote:

And from the chroot look at
journalctl -b -1
The kernel commandline will tell you whether you're booting from the root or boot partition (look whether the location of the kernel contains "/boot" - if not, you're booting from a boot partition)

The kernel command line says:

Kernel command line: BOOT_IMAGE=vmlinuz-linux root=/dev/mapper/volgroup0-lvroot […]

So that tells me that boot isn’t mounted if I understand correctly?

So, I have to mount the boot partition before running mkinitcpio, right? By doing the following?

mount /dev/nvme0n1p1 /boot

Nvme0n1p1 shows under fdisk -l as a EFI system so I presume that is my boot partition?

seth · 2022-11-10 15:59:28

So, I have to mount the boot partition before running mkinitcpio, right?

Yes.
You can mount nvme0n1p1 and look at it - if there're some kernels and initramfs etc. flying around, it's likely the boot partition.

d.ALT · 2022-11-10 16:01:43

F178 wrote:

So, I have to mount the boot partition before running mkinitcpio, right? By doing the following?
mount /dev/nvme0n1p1 /boot
Nvme0n1p1 shows under fdisk -l as a EFI system so I presume that is my boot partition?

So in your case EFI is ESP.
Your /boot is under / within the same partition; and your ESP is inside /boot/efi which resides onto another partition.

Please, as seth asked you, post here the complete lsblk -f output.

F178 · 2022-11-10 16:04:25

seth wrote:

So, I have to mount the boot partition before running mkinitcpio, right?
Yes.
You can mount nvme0n1p1 and look at it - if there're some kernels and initramfs etc. flying around, it's likely the boot partition.

Very good.

I’ve mounted nvme0n1p1 but that only has a directory called EFI

nvme0n1p2 on the other hand has EFI, grub, and a bunch of initramfs lying around.

So that means I should mount the second one as boot and then run mkinitcpio again, correct?

seth · 2022-11-10 16:10:32

lsblk -f 
ls -l /boot # w/ nvme0n1p2 mounted there

Edit: you can upload that following the tip in the 1st link below. In doubt *link* (don't embed) a photo.
Do NOT post some OCR scan!

Last edited by seth (2022-11-10 16:11:37)

F178 · 2022-11-10 16:29:15

As per that most recent tip, here are the two outputs per photo. Pastebin isn’t really an option, the Wi-Fi setup is complicated so I don’t have internet access on the machine right now, sorry.

https://pasteboard.co/ekindSUouM8V.jpg
https://pasteboard.co/mXQfEBMiyI3l.jpg

seth · 2022-11-10 16:34:18

There's also your lts kernel w/ timestamps from very early this morning.
Looks very much like nvme0n1p2 is your boot partition, so run mkinitcpio w/ that partition being mounted and reboot.
If everything works afterwards, you want to clean up the UNMOUNTED /boot path

d.ALT · 2022-11-10 16:35:08

From the Live environment you have to mount RootPartition inside /mnt and BootPartition inside /mnt/boot (and you ESP should be mounted inside /mnt/boot/efi).

F178 · 2022-11-10 17:12:08

This worked, thank you very much both of you. You really helped me out of some deep trouble here! And I refreshed my knowledge about mount points, the different partitions etc. that I had forgotten since installing.

In case anyone runs into a similar problem. The procedure that finally solved it was:

# cryptsetup open /dev/nvme0n1p3 archfilesys
(enter the password for encrypted drive)
# lvchange -ay volgroup0
# mount /dev/volgroup0/lv_root /mnt
# mount /dev/nvme0n1p2 /mnt/boot
# mount /dev/nvme0n1p1 /mnt/boot/EFI
# arch-chroot /mnt
[root@archiso /] # mkinitcpio -P

Then I rebooted and everything went smoothly.

seth wrote:

If everything works afterwards, you want to clean up the UNMOUNTED /boot path

Would you be so kind as to explain that point? If I understood everything correctly I might now have a /boot directory with some un-needed images lying around somewhere, because I ran mkinitcpio without the /boot directory mounted? How can I locate that? The only thing I see from within the system is the correct /boot directory with the proper folders etc.

Again, thanks for your help, very much appreciated!

d.ALT · 2022-11-10 17:15:37

F178 wrote:

How can I locate that?

Your /etc/fstab will tell you everyhting you need to know. Look inside it: is there any /boot declared?

Last edited by d.ALT (2022-11-10 17:16:28)

F178 · 2022-11-10 17:22:12

d.ALT wrote:

F178 wrote:
How can I locate that?
Your /etc/fstab will tell you everyhting you need to know. Look inside it: is there any /boot declared?

Yes!

# /dev/nvme0n1p2
UUID=58a3ca06-3397-4ba0-bf40-4bba587a7a34       /boot           ext4            rw,relatime     0 2

And that seems to be correct doesn't it? It specifies that nvme0n1p2 is always to be mounted at /boot

d.ALT · 2022-11-10 17:28:26

OK. So seth was suggesting you to clean the other /boot.
But PAY ATTENTION!: if you clean-up the /boot directory after you booted into Arch, you're going to delete the actual files inside nvme0n1p2! DON'T DO THAT!!

seth · 2022-11-10 20:34:34

You just need to "umount /boot" - afterwards, the /boot path should only contain the bogus files you placed there while trying to fix the system.
You can also

findmnt /boot

to make sure nothing is mounted there.

You can then remove those bogus files - it's not strictly necessary, but
1. you'll get a warning everytime you mount /boot because the path isn't empty
2. you gain some space on your disk
3. they won't confuse you in the future

Arch Linux

#1 2022-11-10 14:28:58

[SOLVED] Libcrypt.so.3 cannot open and a further problem

#2 2022-11-10 14:44:22

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#3 2022-11-10 14:45:04

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#4 2022-11-10 15:12:31

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#5 2022-11-10 15:22:03

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#6 2022-11-10 15:23:47

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#7 2022-11-10 15:31:03

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#8 2022-11-10 15:37:29

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#9 2022-11-10 15:39:59

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#10 2022-11-10 15:41:41

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#11 2022-11-10 15:56:37

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#12 2022-11-10 15:59:28

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#13 2022-11-10 16:01:43

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#14 2022-11-10 16:04:25

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#15 2022-11-10 16:10:32

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#16 2022-11-10 16:29:15

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#17 2022-11-10 16:34:18

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#18 2022-11-10 16:35:08

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#19 2022-11-10 17:12:08

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#20 2022-11-10 17:15:37

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#21 2022-11-10 17:22:12

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#22 2022-11-10 17:28:26

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

#23 2022-11-10 20:34:34

Re: [SOLVED] Libcrypt.so.3 cannot open and a further problem

Board footer