System Crash during update

Changed the line to
SigLevel = Optional TrustAll

The whole packages are downloading again :confused:

Total (   4/2221) 
``

cancel it, and rerun update only:

sudo pacman --sysroot /mnt -Syu

Same error:

rning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
error: xz: missing required signature
:: File /var/cache/pacman/pkg/xz-5.2.7-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Y
error: apache: missing required signature
:: File /var/cache/pacman/pkg/apache-2.4.54-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Y
error: cairomm: missing required signature
:: File /var/cache/pacman/pkg/cairomm-1.14.4-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Y
error: pango: missing required signature
:: File /var/cache/pacman/pkg/pango-1:1.50.11-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: hwdata: missing required signature
:: File /var/cache/pacman/pkg/hwdata-0.363-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: xkeyboard-config: missing required signature
:: File /var/cache/pacman/pkg/xkeyboard-config-2.37-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: code: missing required signature
:: File /var/cache/pacman/pkg/code-1.72.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: dconf-editor: missing required signature
:: File /var/cache/pacman/pkg/dconf-editor-43.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
:: File /var/cache/pacman/pkg/yelp-xsl-42.1-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

in pacman.conf there are lines:

[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

[community]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist

Maybe sigLevel also change?

Changed this and rerun sudo pacman --sysroot /mnt -Syu and still the same error

chnaged to NEVER and packages are upgrading

ok good, hopefully no more errors

==> Generating module dependencies
awk: symbol lookup error: awk: undefined symbol: exp, version GLIBC_2.29
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.19-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
(11/20) Updating Kernel initcpios for Nvidia-DRM...
(12/20) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.19-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.19-x86_64.img
Found initrd fallback image: /boot/initramfs-5.19-x86_64-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
fgrep: warning: fgrep is obsolescent; using grep -F
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
(13/20) Reloading system bus configuration...
  Skipped: Running in chroot.
(14/20) Warn about old perl modules
perl: symbol lookup error: /usr/lib/perl5/5.36/core_perl/CORE/libperl.so: undefined symbol: exp, version GLIBC_2.29
WARNING: '/usr/lib/perl5/5.36' contains data from at least 112 packages which will NOT be used by the installed perl interpreter.
 -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/5.36'
(15/20) Copy Firefox Distribution Settings
(16/20) Compiling GSettings XML schema files...
No such key “bulk-rename-tool” in schema “org.gnome.nautilus.preferences” as specified in override file “/usr/share/glib-2.0/schemas/50_nautilus-renamer.gschema.override”; ignoring override for this key.
(17/20) Updating icon theme caches...
gtk-update-icon-cache: symbol lookup error: /usr/lib/libtiff.so.5: undefined symbol: exp, version GLIBC_2.29
error: command failed to execute correctly
(18/20) Updating the info directory file...
(19/20) Updating the desktop file MIME type cache...
(20/20) Updating the vlc plugin cache...
Failed loading SDL2 library.
error: command terminated by signal 6: Aborted

ech how to reinstall this glib c :expressionless:

try with overwrite:
sudo pacman --sysroot /mnt -S glibc --overwrite '*'

warning: glibc-2.36-5 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) glibc-2.36-5

Total Installed Size:  47.36 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                                                                                                 [#############################################################################] 100%
(1/1) checking package integrity                                                                                               [#############################################################################] 100%
(1/1) loading package files                                                                                                    [#############################################################################] 100%
(1/1) checking for file conflicts                                                                                              [#############################################################################] 100%
(1/1) checking available disk space                                                                                            [#############################################################################] 100%
warning: could not get file information for var/db/Makefile
:: Processing package changes...
(1/1) reinstalling glibc                                                                                                       [#############################################################################] 100%
Generating locales...
  en_US.UTF-8... done
  pl_PL.UTF-8... done
Generation complete.
:: Running post-transaction hooks...
(1/5) Reloading system manager configuration...
  Skipped: Running in chroot.
(2/5) Creating temporary files...
Failed to open file "/sys/devices/system/cpu/microcode/reload": Read-only file system
error: command failed to execute correctly
(3/5) Arming ConditionNeedsUpdate...
(4/5) Restarting cronie for libc upgrade...
Running in chroot, ignoring command 'try-restart'
(5/5) Updating the info directory file...

hm… it is reinstalled?

yes it reinstalled, so rerun the update again:

sudo pacman --sysroot /mnt -Syu
[manjaro-gnome manjaro]# sudo pacman --sysroot /mnt -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do

oh … should I reboot?

I think I should run command to find the kernel and update the grub?

check first this:
mhwd-kernel -li

Currently running: 5.15.60-1-MANJARO (linux515)
The following kernels are installed in your system:
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'community' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
   * linux515
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'community' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)

close the terminal, open terminal, chroot, and check kernels:
mhwd-kernel -li

    ~  manjaro-chroot -a                                                ✔ 
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
==> Mounting (ManjaroLinux) [/dev/nvme0n1p1]
 --> mount: [/mnt]
mount: /mnt: /dev/nvme0n1p1 already mounted on /mnt.
       dmesg(1) may have more information after failed mount system call.
 --> mount: [/mnt/boot/efi]
mount: /mnt/boot/efi: /dev/nvme0n1p4 already mounted on /mnt/boot/efi.
       dmesg(1) may have more information after failed mount system call.
mount: /mnt/sys: sys already mounted on /sys.
       dmesg(1) may have more information after failed mount system call.
[manjaro-gnome /]# mhwd-kernel -li
Currently running: 5.15.60-1-MANJARO (linux515)
The following kernels are installed in your system:
   * linux510
   * linux515
   * linux519
[manjaro-gnome /]# ^C
[manjaro-gnome /]# 

so no end of life kernels, reboot and see if it helped

2 Likes

YEAH!!!
The kernel inux519 after picking shows errors but when I’ve changed to 5.15.72-1-MANJARO (linux515) the system STARTS!!

YOU R AWESOME! Thanks a lot.
Ech. Should I update the system again? What I did wrong?

yes rerun update again, then uninstall the linux519, then install it again, reboot and try boot with it…
i dont know what did you do when the system crashed during updating… maybe you didnt do anything and it just crashed, that happens…

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.