[SOLVED] Pacman -Syu Update Fail - Openssl

cfr · 2017-10-14 23:43:50

zpg443 wrote:

 2      316MB   419MB  104MB  fat32        EFI system partition          boot, esp
 
 1      1049kB  538MB  537MB   fat32                 boot, esp

 4      326GB   326GB  629MB   fat32           sdb4  boot, esp

You should have a **single** ESP.. Here, sda2 is marked as your EFI partition. If needs be, you can have multiple boot partitions, by separating the boot partition from the EFI partition. But at most one of those should be your EFI system partition. However, this is more complex than mounting the EFI at /boot.

If sda2 is your ESP and you want to use sdb4 as boot for Arch, then you need to mount the boot partition first and then mount the ESP to /boot/efi or something like that. grub can use a kernel and initrd on another partition. You can look at the command line grub is trying to boot with or examine grub.cfg if you have access to the system.

zpg443 · 2017-10-15 04:08:46

seth wrote:

Check the kernel version you boot
uname -a
Then boot the installation medium and mount sdb1 and sdb4 (it doesn't matter where, you can mount them into /tmp/sdb1 & /tmp/sdb4 and umount them afterwards) and check whether and which linux kernel is in either partition:
file /boot/vmlinuz-linux
One of them should match the "uname -a" version, the other (if exists) likely not.
The one with the matching version is your boot partition. Mount that into /mnt/boot (after of course mounting sdb5 into /mnt)
NOTICE: that the device names can be arbitrary: ensure that /dev/sdb5 contains your archlinux!
Then re-install the inux package.
Reboot.

Ok I am going to try this.

cfr wrote:

zpg443 wrote:
 2      316MB   419MB  104MB  fat32        EFI system partition          boot, esp
 
 1      1049kB  538MB  537MB   fat32                 boot, esp

 4      326GB   326GB  629MB   fat32           sdb4  boot, esp
You should have a **single** ESP.. Here, sda2 is marked as your EFI partition. If needs be, you can have multiple boot partitions, by separating the boot partition from the EFI partition. But at most one of those should be your EFI system partition. However, this is more complex than mounting the EFI at /boot.

Windows on sda:

 2      316MB   419MB  104MB  fat32        EFI system partition          boot, esp

Debian 9 on sdb1:

 1      1049kB  538MB  537MB   fat32                 boot, esp

Arch on sdb4:

  4      326GB   326GB  629MB   fat32           sdb4  boot, esp

I assume there are 3 boot records because my system has three operating systems.

cfr wrote:

If sda2 is your ESP and you want to use sdb4 as boot for Arch, then you need to mount the boot partition first and then mount the ESP to /boot/efi or something like that. grub can use a kernel and initrd on another partition. You can look at the command line grub is trying to boot with or examine grub.cfg if you have access to the system.

Good point. When first tried this, I tried

 mount /mnt /boot/efi

but that did not work. I use grub (installed with debian) to manage the windows boot manager, and to launch arch. The menu entry for Arch in the grub.cfg file is:

menuentry 'Arch Linux (rolling) (on /dev/sdb5)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-501b3586-3209-4a0f-9430-5277481cc725' {
	insmod part_gpt
	insmod fat
	set root='hd1,gpt4'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4  F162-F3B0
	else
	  search --no-floppy --fs-uuid --set=root F162-F3B0
	fi
	linux /vmlinuz-linux root=/dev/sdb5
	initrd /initramfs-linux.img

I know one of the many mistakes I made trying to fix this was I did not do umount on all partitions prior to rebooting.
Also, because I have never done a repair before, I am not clear what install steps I can skip or need to avoid to keep my apps and configuration intact.

Last edited by zpg443 (2017-10-15 04:10:47)

zpg443 · 2017-10-15 06:34:38

seth wrote:

Check the kernel version you boot
uname -a
Then boot the installation medium and mount sdb1 and sdb4 (it doesn't matter where, you can mount them into /tmp/sdb1 & /tmp/sdb4 and umount them afterwards) and check whether and which linux kernel is in either partition:
file /boot/vmlinu[b]z[/b]-linux
One of them should match the "uname -a" version, the other (if exists) likely not.
The one with the matching version is your boot partition. Mount that into /mnt/boot (after of course mounting sdb5 into /mnt)
NOTICE: that the device names can be arbitrary: ensure that /dev/sdb5 contains your archlinux!
Then re-install the linux package.
Reboot.

sdb4 has the version matching the one booting into emergency mode, 4.10.8-1-ARCH.
sdb1 does not have an image. It has the debian EFI.
Yes I am sure sdb5 has my arch installation.

Here is what happened after boot with install disk:

mount /dev/sdb5 /mnt
mount /dev/sdb4/ mnt/boot
mount -t proc /dev/sdb5 /mnt/proc
mount -t sysfs /dev/sdb5 /mnt/sys
rm /lib/libcrypto.so.1.1
rm /lib/libssl.so.1.1
rm /lib64/libcrypto.so.1.1
rm /lib64/libssl.so.1.1
chroot /mnt /bin/bash
pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syyu

Result:

Error while loading shared libraries : libcrypto.so.1.1 Cannot open shared object file : no such file or directory

I mentioned earlier in this thread another user who posted a solution said this issue could not be fixed by repairing with the install disk.

seth wrote:

Then re-install the linux package.

What specifically do you mean by this?

pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syyu

or

pacstrap /mnt base vim git sudo

I want to rescue my current install if possible. Is this a hopeless cause?

Last edited by zpg443 (2017-10-19 16:30:12)

seth · 2017-10-15 06:54:40

How did you install archlinux itfp?

zpg443 wrote:

mount /dev/sdb4/mnt/boot

Did you miss the the error message this will have yelled?

zpg443 wrote:

rm /lib/libcrypto.so.1.1
rm /lib/libssl.so.1.1
rm /lib64/libcrypto.so.1.1
rm /lib64/libssl.so.1.1

So you deleted those libraries from the installation medium??

zpg443 wrote:

chroot /mnt /bin/bash
pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syyu

Eitherchroot XOR set /mnt as root dir to pacman.
Since you deleted libcrypto, this failed expectably ... m(

1. Don't "-Syyu" unless you know why you're typing two "y"'s there - "-Syu" is regularily sufficient
2. Get a fresh installation image (unless you had written the other to a non-writable CD), because you probably severely damaged the existing one
3. Follow the guide loqs linked. That is not the same as copy-pasting random commands in random order! - Hint: you won't have to chroot at all in this case
4. Look at the "mount" manpge. Spoiler alert: "mount <what> <where>" - there should be a blank inbetween
5. "Then re-install the linux package." means to "Then re-install the linux package." - not to re-install archlinux or something. Hint: This one.

zpg443 · 2017-10-15 14:04:44

I appreciate your patience, and will study/focus on all of this much more carefully before acting. I am using a fresh CD-ROM ISO image, and I included the space when I did

mount /dev/sdb4 /mnt/boot

.

Last edited by zpg443 (2017-10-15 14:07:40)

cfr · 2017-10-15 18:09:31

I assume there are 3 boot records because my system has three operating systems.

Yes, but you should have only ONE ESP. It is easier to have this be the boot partition, but not required.

If you are using Debian's grub, did you boot Debian and reconfigure grup there?

zpg443 · 2017-10-17 16:48:43

I was finally able to do pacman --root -Syu successfully. I then booted into my debian install and ran update grub, but upon rebooting into Arch, got a kernel panic. I probably needed to have chrooted and run mkinitcpio -p linux in after pacman --root -Syu, and before updating grub. There was an intel microcode update that didn't appear as a new image next to the boot image. It is still showing the older microcode image even though the pacman log shows it was updated.

Since Arch was updated to 4.13.6-1, but the latest ISO available for my boot disk is 4.13.5-1, I cannot get back in yet to run mkinitcpio -p linux. I assume I will need to wait until a newer image is available.

Last edited by zpg443 (2017-10-17 16:49:03)

loqs · 2017-10-17 20:39:41

zpg443 wrote:

Since Arch was updated to 4.13.6-1, but the latest ISO available for my boot disk is 4.13.5-1, I cannot get back in yet to run mkinitcpio -p linux. I assume I will need to wait until a newer image is available.

Why would the kernel on the boot media need to match the installed kernel?

cfr · 2017-10-18 04:04:08

zpg443 wrote:

I was finally able to do pacman --root -Syu successfully. I then booted into my debian install and ran update grub, but upon rebooting into Arch, got a kernel panic. I probably needed to have chrooted and run mkinitcpio -p linux in after pacman --root -Syu, and before updating grub. There was an intel microcode update that didn't appear as a new image next to the boot image. It is still showing the older microcode image even though the pacman log shows it was updated.
Since Arch was updated to 4.13.6-1, but the latest ISO available for my boot disk is 4.13.5-1, I cannot get back in yet to run mkinitcpio -p linux. I assume I will need to wait until a newer image is available.

Sounds like you did not have your boot partition mounted correctly during the update. So probably the kernel and initrd are the old versions, too. This would surely cause a kernel panic. (Much more likely than the outdated microcode, in fact.)

zpg443 · 2017-10-19 22:21:06

cfr wrote:

zpg443 wrote:
I was finally able to do pacman --root -Syu successfully. I then booted into my debian install and ran update grub, but upon rebooting into Arch, got a kernel panic. I probably needed to have chrooted and run mkinitcpio -p linux in after pacman --root -Syu, and before updating grub. There was an intel microcode update that didn't appear as a new image next to the boot image. It is still showing the older microcode image even though the pacman log shows it was updated.
Since Arch was updated to 4.13.6-1, but the latest ISO available for my boot disk is 4.13.5-1, I cannot get back in yet to run mkinitcpio -p linux. I assume I will need to wait until a newer image is available.
Sounds like you did not have your boot partition mounted correctly during the update. So probably the kernel and initrd are the old versions, too. This would surely cause a kernel panic. (Much more likely than the outdated microcode, in fact.)

I installed vmlinuz-linux twice because the last time I ran pacman --root -Syu, I did not properly mount /sdb4/mnt as /mnt/boot, so it updated instead to sdb5/boot. I am guessing grub2 detected the wrong image (see comments about grub at bottom), and it found no initramfs-linux.img or backup on sdb5, so it went into panic?

Mounting only sdb5 and checking for the image:

mount /dev/sdb5 /mnt
cd /mnt/boot
file /boot/vmlinuz-linux

Returns the version of 4.13.5-1. There is no initramfs-linux.img or backup img in the dir.

Next, check sdb4. Mount /boot to sdb4:

mount /dev/sdb5 /mnt
mount /dev/sdb4 /mnt/boot
cd /mnt/boot
file /boot/vmlinuz-linux

Now it returns the version of 4.13.6-1. Note sdb4/boot includes both the initramfs-linux.img and backup (created on 7 Apr 2017).

Note that the newer intel microcode update installed in sdb5/boot, while sdb4/boot still has the old one. I don't know if I should copy that file from sdb5 to sdb 4, or will pacman figure it out?

I would first need to delete the boot dir and contents from sdb5, then mount everything correctly (with boot mounted to sdb4) and re-run pacman --root -Syu. Correct?

Grub.cfg (installed on a separate partition for debian) currently shows this for the arch install:

menuentry 'Arch Linux (rolling) (on /dev/sdb5)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-501b3586-3209-4a0f-9430-5277481cc725' {
	insmod part_gpt
	insmod fat
	set root='hd1,gpt4'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4  F162-F3B0
	else
	  search --no-floppy --fs-uuid --set=root F162-F3B0
	fi
	linux /vmlinuz-linux root=/dev/sdb5

Shouldn't the last line say:

linux /vmlinuz-linux root=/dev/sdb4

because line 4 says:

set root='hd1,gpt4'

...or should it be the other way around?

Last edited by zpg443 (2017-10-19 22:35:50)

loqs · 2017-10-19 22:39:00

I would suggest using Persistent_block_device_naming as identifiers such as /dev/sdb4 can change

cfr · 2017-10-19 22:44:23

Mount the partition which has the root of your entire Arch install to /mnt.

mount /dev/sdb5 /mnt

Check this is correct.

less /mnt/etc/os-release

should give you something like

NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
ID_LIKE=archlinux
ANSI_COLOR="0;36"
HOME_URL="https://www.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"

Then I would backup your current boot.

cp -pr /mnt/boot /mnt/boot.bkup

Now remove the files which shouldn't be there

rm /mnt/boot/vmlinuz-linux ...

Now mount your boot partition.

mount /dev/sdb4 /mnt/boot

Check what is there

ls /mnt/boot/

to see if it is what you expect.
Now reinstall linux and microcode

pacman --root=/mnt -Syu linux intel-ucode

I'm pretty sure the

	linux /vmlinuz-linux root=/dev/sdb5

is correct, assuming /dev/sdb5 is the root of your Arch install. It would be better to use something less fickle that /dev/sdb5, but now is probably not the time to worry about that.

The first 'root' is the root of the partition where the kernel and initrd image live. The second 'root' is the root of the main file system. These will not be the same if you have a distinct partition for boot.

Last edited by cfr (2017-10-19 22:47:30)

cfr · 2017-10-19 22:46:50

The first 'root' is the root of the partition where the kernel and initrd image live. The second 'root' is the root of the main file system. These will not be the same if you have a distinct partition for boot.

Last edited by jasonwryan (2017-10-20 00:30:34)

zpg443 · 2017-10-19 23:50:22

Update failed. pacman.log:

[2017-10-19 23:19] [PACMAN] Running 'pacman --root=/mnt -Syu linux intel-ucode'
[2017-10-19 23:19] [PACMAN] synchronizing package lists
[2017-10-19 23:20] [PACMAN] starting full system upgrade
[2017-10-19 23:23] [PACMAN] Running 'pacman --root=/mnt -Syu linux intel-ucode'
[2017-10-19 23:23] [PACMAN] synchronizing package lists
[2017-10-19 23:23] [PACMAN] starting full system upgrade
[2017-10-19 23:24] [ALPM] transaction started
[2017-10-19 23:24] [ALPM] upgraded libsystemd (235.0-1 -> 235.8-1)
[2017-10-19 23:24] [ALPM] upgraded systemd (235.0-1 -> 235.8-1)
[2017-10-19 23:24] [ALPM] upgraded linux (4.13.6-1 -> 4.13.7-1)
[2017-10-19 23:24] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2017-10-19 23:24] [ALPM] reinstalled intel-ucode (20170707-1)
[2017-10-19 23:24] [ALPM] upgraded archlinux-keyring (20170823-1 -> 20171013-1)
[2017-10-19 23:24] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2017-10-19 23:24] [ALPM-SCRIPTLET] key 6BC26A17B9B7018A:
[2017-10-19 23:24] [ALPM-SCRIPTLET] 4 signatures not checked due to missing keys
[2017-10-19 23:24] [ALPM-SCRIPTLET] key 2E89012331361F01:
[2017-10-19 23:24] [ALPM-SCRIPTLET] 1 signature not checked due to a missing key
[2017-10-19 23:24] [ALPM-SCRIPTLET] key EEEEE2EEEE2EEEEE:
[2017-10-19 23:24] [ALPM-SCRIPTLET] 6 signatures not checked due to missing keys
[2017-10-19 23:24] [ALPM-SCRIPTLET] key 6D1655C14CE1C13E:
[2017-10-19 23:24] [ALPM-SCRIPTLET] 1 signature not checked due to a missing key
[2017-10-19 23:24] [ALPM-SCRIPTLET] key 9C02FF419FECBE16:
[2017-10-19 23:24] [ALPM-SCRIPTLET] 4 signatures not checked due to missing keys
[2017-10-19 23:24] [ALPM-SCRIPTLET] sig!         A88E23E377514E00 2017-05-23  Florian Pritz (Arch Linux Master Key) <florian@master-
[2017-10-19 23:24] [ALPM-SCRIPTLET] sub  69A65012074901CB
[2017-10-19 23:24] [ALPM-SCRIPTLET] sig!         EB763B4E9DB887A6 2017-05-22  [self-signature]
[2017-10-19 23:24] [ALPM-SCRIPTLET] key EB763B4E9DB887A6:
[2017-10-19 23:24] [ALPM-SCRIPTLET] 1 signature reordered
[2017-10-19 23:24] [ALPM-SCRIPTLET] key A5E9288C4FA415FA:
[2017-10-19 23:24] [ALPM-SCRIPTLET] 5 signatures not checked due to missing keys
[2017-10-19 23:24] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2017-10-19 23:24] [ALPM-SCRIPTLET]   -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
[2017-10-19 23:24] [ALPM-SCRIPTLET] ==> ERROR: DDB867B92AA789C165EEFA799B729B06A680C281 could not be locally signed.
[2017-10-19 23:24] [ALPM-SCRIPTLET]   -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
[2017-10-19 23:24] [ALPM-SCRIPTLET] ==> ERROR: 684148BB25B49E986A4944C55184252D824B18E8 could not be locally signed.
[2017-10-19 23:24] [ALPM-SCRIPTLET]   -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
[2017-10-19 23:24] [ALPM-SCRIPTLET] ==> ERROR: 91FFE0700E80619CEB73235CA88E23E377514E00 could not be locally signed.
[2017-10-19 23:24] [ALPM-SCRIPTLET]   -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2017-10-19 23:24] [ALPM-SCRIPTLET] ==> ERROR: AB19265E5D7D20687D303246BA1DFB64FFF979E7 could not be locally signed.
[2017-10-19 23:24] [ALPM-SCRIPTLET]   -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2017-10-19 23:24] [ALPM-SCRIPTLET] ==> ERROR: 0E8B644079F599DFC1DDC3973348882F6AC6A4C2 could not be locally signed.
[2017-10-19 23:24] [ALPM-SCRIPTLET]   -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
[2017-10-19 23:24] [ALPM-SCRIPTLET] ==> ERROR: 44D4A033AC140143927397D47EFD567D4C7EA887 could not be locally signed.
[2017-10-19 23:24] [ALPM] upgraded libdrm (2.4.83-1 -> 2.4.84-1)
[2017-10-19 23:24] [ALPM] upgraded kdecoration (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded thin-provisioning-tools (0.7.3-2 -> 0.7.4-1)
[2017-10-19 23:24] [ALPM] upgraded breeze (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded celt (0.11.3-2 -> 0.11.3-3)
[2017-10-19 23:24] [ALPM] upgraded freeglut (3.0.0-1 -> 3.0.0-2)
[2017-10-19 23:24] [ALPM] upgraded gtk-update-icon-cache (3.22.24+72+g841b879aed-1 -> 3.22.24+80+g6a4be7f56b-1)
[2017-10-19 23:24] [ALPM] upgraded gtk3 (3.22.24+72+g841b879aed-1 -> 3.22.24+80+g6a4be7f56b-1)
[2017-10-19 23:24] [ALPM] upgraded gtk3-print-backends (3.22.24+72+g841b879aed-1 -> 3.22.24+80+g6a4be7f56b-1)
[2017-10-19 23:24] [ALPM] upgraded kactivitymanagerd (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded kde-cli-tools (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded kde-gtk-config (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded libksysguard (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded ktexteditor (5.39.0-1 -> 5.39.0-2)
[2017-10-19 23:24] [ALPM] upgraded milou (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded kscreenlocker (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded kwin (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded noto-fonts (20170920-2 -> 20171019-2)
[2017-10-19 23:24] [ALPM] upgraded plasma-integration (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded kuiserver (5.11.0-2 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded plasma-workspace (5.11.0-2 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded kdeplasma-addons (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded khotkeys (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded kmenuedit (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded knetattach (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded libkscreen (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded kscreen (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded ksysguard (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded libmm-glib (1.6.8-1 -> 1.6.10-1)
[2017-10-19 23:24] [ALPM] upgraded modemmanager (1.6.8-1 -> 1.6.10-1)
[2017-10-19 23:24] [ALPM] upgraded netctl (1.13-2 -> 1.14-1)
[2017-10-19 23:24] [ALPM] warning: /mnt/etc/pacman.d/mirrorlist installed as /mnt/etc/pacman.d/mirrorlist.pacnew
[2017-10-19 23:24] [ALPM] upgraded pacman-mirrorlist (20170907-1 -> 20171017-1)
[2017-10-19 23:24] [ALPM] upgraded polkit-kde-agent (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded systemsettings (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded plasma-desktop (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded sddm-kcm (5.11.0-1 -> 5.11.1-1)
[2017-10-19 23:24] [ALPM] upgraded systemd-sysvcompat (235.0-1 -> 235.8-1)
[2017-10-19 23:24] [ALPM] transaction completed
[2017-10-19 23:24] [ALPM] running '90-linux.hook'...
[2017-10-19 23:24] [ALPM-SCRIPTLET] ==> ERROR: /proc must be mounted!
[2017-10-19 23:24] [ALPM] running 'fontconfig.hook'...
[2017-10-19 23:24] [ALPM] running 'glib-compile-schemas.hook'...
[2017-10-19 23:24] [ALPM] running 'gtk-query-immodules-3.0.hook'...
[2017-10-19 23:24] [ALPM] running 'gtk-update-icon-cache.hook'...
[2017-10-19 23:24] [ALPM] running 'systemd-hwdb.hook'...
[2017-10-19 23:24] [ALPM] running 'systemd-sysusers.hook'...
[2017-10-19 23:24] [ALPM] running 'systemd-tmpfiles.hook'...
[2017-10-19 23:24] [ALPM-SCRIPTLET] ACL operation on "/var/log/journal" failed: No such file or directory
[2017-10-19 23:24] [ALPM-SCRIPTLET] ACL operation on "/var/log/journal" failed: No such file or directory
[2017-10-19 23:24] [ALPM-SCRIPTLET] ACL operation on "/var/log/journal/3cf7730ad4cf412ba4ee9eda3c86dc3f" failed: No such file or directory
[2017-10-19 23:24] [ALPM-SCRIPTLET] ACL operation on "/var/log/journal/3cf7730ad4cf412ba4ee9eda3c86dc3f" failed: No such file or directory
[2017-10-19 23:24] [ALPM-SCRIPTLET] ACL operation on "/var/log/journal/3cf7730ad4cf412ba4ee9eda3c86dc3f/system.journal" failed: No such file or directory
[2017-10-19 23:24] [ALPM-SCRIPTLET] [tmp.conf:15] Failed to replace specifiers: /tmp/systemd-private-%b-*
[2017-10-19 23:24] [ALPM-SCRIPTLET] [tmp.conf:16] Failed to replace specifiers: /tmp/systemd-private-%b-*/tmp
[2017-10-19 23:24] [ALPM-SCRIPTLET] [tmp.conf:17] Failed to replace specifiers: /var/tmp/systemd-private-%b-*
[2017-10-19 23:24] [ALPM-SCRIPTLET] [tmp.conf:18] Failed to replace specifiers: /var/tmp/systemd-private-%b-*/tmp
[2017-10-19 23:24] [ALPM] running 'systemd-update.hook'...
[2017-10-19 23:24] [ALPM] running 'update-desktop-database.hook'...
[2017-10-19 23:24] [ALPM] running 'xorg-mkfontdir.hook'...
[2017-10-19 23:24] [ALPM-SCRIPTLET] sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

I saw that some keys needed to be updated, and that proc was not mounted (my fault again, failed to mount proc and sys). To make matters worse, the original problem with openssl appears to still be there:

error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

I mounted proc and sys...

mount - t proc /dev/sdb5 /mnt/proc
mount - t sysfs /dev/sdb5 /mnt/sys

.. and tried again in hopes that would fix the issue:

[2017-10-19 23:28] [PACMAN] Running 'pacman --root=/mnt -Syu linux intel-ucode'
[2017-10-19 23:28] [PACMAN] synchronizing package lists
[2017-10-19 23:28] [PACMAN] starting full system upgrade
[2017-10-19 23:28] [ALPM] transaction started
[2017-10-19 23:28] [ALPM] reinstalled linux (4.13.7-1)
[2017-10-19 23:28] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2017-10-19 23:28] [ALPM] reinstalled intel-ucode (20170707-1)
[2017-10-19 23:28] [ALPM] transaction completed
[2017-10-19 23:28] [ALPM] running '90-linux.hook'...
[2017-10-19 23:28] [ALPM-SCRIPTLET] ==> ERROR: /dev must be mounted!
[2017-10-19 23:28] [ALPM] running 'systemd-update.hook'...

It didn't work, and it apparently got stuck while running systemd-update.hook. I was not able to unmount. There is some issue with libalpm.
/usr/share/libalpm/hooks/90-linux.hook:

[Trigger]
Type = File
Operation = Install
Operation = Upgrade
Target = boot/vmlinuz-linux
Target = usr/lib/initcpio/*

[Action]
Description = Updating linux initcpios
When = PostTransaction
Exec = /usr/bin/mkinitcpio -p linux

From Arch Wiki:

"/dev must be mounted" when it already is

The test used by mkinitcpio to determine if /dev is mounted is to see if /dev/fd/ is there. If everything else looks fine, it can be "created" manually by:

# ln -s /proc/self/fd /dev/

(Obviously, /proc must be mounted as well. mkinitcpio requires that anyway, and that is the next thing it will check.)

Last edited by zpg443 (2017-10-20 00:15:34)

zpg443 · 2017-10-21 00:30:27

I appreciate all of the assistance, and although I still have an issue, I am closing out this thread as it has been cluttered with all of my newbie mistakes. I am grateful for the support and I have already learned much from working this issue. I might start a new thread if I don't just reinstall arch from scratch.

NoSuck · 2017-10-21 07:53:18

You can upgrade in small increments after the fact. (I wish I could have told you before the fact.)

zpg443 · 2017-10-22 14:39:36

Here is how I finally fixed the openssl problem (from my newbie point of view)

1. Burn the latest arch iso to a USB or CD-ROM

2. Boot your computer into the arch iso

3. Mount these (where x is the partition where arch and/or boot partition is installed):

mount /dev/sdx /mnt
mount -t vfat [or other partition format] /dev/sdx/ mnt/boot
mount -t proc /dev/sdx /mnt/proc
mount -t sysfs /dev/sdx /mnt/sys
mount -t devtmpfs /dev/sdx /mnt/dev

4. Now run pacman root:

pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syu

The update may fail even with pacman --root. If so, remove (after relocating) the offending libcrypto and libssl files, like those seen in this message:

error: failed to commit transaction (conflicting files)
openssl: /usr/lib/libcrypto.so.1.1 exists in filesystem
openssl: /usr/lib/libssl.so.1.1 exists in filesystem

rm /lib/libcrypto.so.1.1
rm /lib/libssl.so.1.1

5. pacman should now update, but fail to generate a new image:

[ALPM-SCRIPTLET] sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

[ALPM-SCRIPTLET] ==> ERROR: Image generation FAILED: bsdcpio reported an error

6. Unmount

umount -R /mnt

7. Now mount ONLY these two (where x is the partition where arch and/or boot partition is installed):

mount /dev/sdx /mnt
mount -t vfat [or other partition format] /dev/sdx/ mnt/boot

8. Reinstall openssl

pacman -r /mnt -Syu openssl

It will complain about missing files, but it will complete.

9. Now run:

pacman -Syu mkinitcpio systemd linux

10. Now, umount and reboot.

Success!

Other sources:

https://www.soimort.org/notes/170407/
https://wiki.archlinux.org/index.php/OpenSSL

Last edited by zpg443 (2017-11-04 15:03:03)

Arch Linux

#26 2017-10-14 23:43:50

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#27 2017-10-15 04:08:46

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#28 2017-10-15 06:34:38

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#29 2017-10-15 06:54:40

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#30 2017-10-15 14:04:44

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#31 2017-10-15 18:09:31

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#32 2017-10-17 16:48:43

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#33 2017-10-17 20:39:41

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#34 2017-10-18 04:04:08

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#35 2017-10-19 22:21:06

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#36 2017-10-19 22:39:00

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#37 2017-10-19 22:44:23

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#38 2017-10-19 22:46:50

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#39 2017-10-19 23:50:22

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#40 2017-10-21 00:30:27

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#41 2017-10-21 07:53:18

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

#42 2017-10-22 14:39:36

Re: [SOLVED] Pacman -Syu Update Fail - Openssl

Board footer