Pamac-manager update post-transaction hooks failures

martins · 21 December 2022 09:38

The last 2 occasions I’ve tried updating my system via pamac-manager I’ve got failures at the post-transaction hooks phase.

The packages download and upgrade but the process gets stuck during the post-transaction hooks with the output shown below. After the first occurence I was unable to get to the login screen and had to resort to getting into the grub menu, restarting into a non-graphical login, then running startx manually. This works and my desktop runs.

I thought this might be a one-off, and waited for another update to see if it would resolve itself. Unfortunately that wasn’t the case. Any ideas on why this might be happening, and what can be done to resolve the issue?

TIA

#### REMOVED LOTS OF PACKAGES FOR BREVITY
Upgrading xorg-xinit (1.4.1-3 -> 1.4.2-1)...
Upgrading zsh (5.9-1 -> 5.9-2)...
Running post-transaction hooks...
Creating system user accounts...
Updating journal message catalog...
Reloading system manager configuration...
Updating udev hardware database...
Applying kernel sysctl settings...
Creating temporary files...
Reloading device manager configuration...
Arming ConditionNeedsUpdate...
Updating the MIME type database...
Rebuilding certificate stores...
Updating module dependencies...
Install DKMS modules
==> dkms install --no-depmod wireguard/1.0.20211208 -k 5.4.228-1-MANJARO
==> depmod 5.4.228-1-MANJARO
Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: 5.4.228-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
loadkeys: Unable to open file: au: No such file or directory
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: 5.4.228-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: bfa
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
loadkeys: Unable to open file: au: No such file or directory
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'default'
  -> -k /boot/vmlinuz-6.1-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.1-x86_64.img
==> Starting build: 6.1.0-1-MANJARO
  -> 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: [keyboard]
  -> Running build hook: [keymap]
loadkeys: Unable to open file: au: No such file or directory
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-6.1-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'fallback'
  -> -k /boot/vmlinuz-6.1-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.1-x86_64-fallback.img -S autodetect
==> Starting build: 6.1.0-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
loadkeys: Unable to open file: au: No such file or directory
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-6.1-x86_64-fallback.img
==> Image generation successful
Updating the appstream cache...
✔ Metadata cache was updated successfully.
Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
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.
ERROR: asr: reading /dev/sdb[Input/output error]
ERROR: ddf1: reading /dev/sdb[Input/output error]
ERROR: ddf1: reading /dev/sdb[Input/output error]
ERROR: hpt37x: reading /dev/sdb[Input/output error]
ERROR: hpt45x: reading /dev/sdb[Input/output error]
ERROR: isw: reading /dev/sdb[Input/output error]
ERROR: jmicron: reading /dev/sdb[Input/output error]
ERROR: lsi: reading /dev/sdb[Input/output error]
ERROR: nvidia: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]
ERROR: pdc: reading /dev/sdb[Input/output error]

Aragorn · 21 December 2022 09:54

You have an I/O error on /dev/sdb, whichever drive that is on your system. So either the drive is dying (or dead already), or it’s an issue with the connector/cable. But it’s definitely a hardware problem.

bogdancovaciu · 21 December 2022 09:57

Please share cat /etc/vconsole.conf

If by chance you have
KEYMAP=au
then look again in /usr/share/kbd/keymaps/i386/ because there is no such thing. Please do not confuse KEYMAP with LANG …

martins · 21 December 2022 21:00

Thanks @bogdancovaciu, here’s the contents of /etc/vconsole.conf

❯ cat /etc/vconsole.conf
KEYMAP=au
FONT=
FONT_MAP=

bogdancovaciu · 21 December 2022 21:10

As expected

Should not be that way because there is no such keymap. Not sure how it came to be that way on your end. This should help Linux console/Keyboard configuration - ArchWiki
or by running from terminal
localectl list-keymaps
you will have all the available list of keymaps, then identify the exact one you want and either edit the file and add the correct one, then run
sudo mkinitcpio -P
so you will not have that error anymore when

Or follow the guide from the wiki to create a custom keymap …
As for the other error, as @Aragorn pointed out already, might want to investigate that.

martins · 22 December 2022 00:52

Thanks @bogdancovaciu, I’ve updated the keymap to us and run sudo mkinitcpio -P.

As for the hardware issue, I ran smartctl against the drive and it is passing:

❯ sudo smartctl -t long -a /dev/nvme0
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-1-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       CA3-8D512-Q11 NVMe LITEON 512GB
Serial Number:                      TW092X04LOH0084J00KS
Firmware Version:                   C49110B
PCI Vendor ID:                      0x14a4
PCI Vendor Subsystem ID:            0x1b4b
IEEE OUI Identifier:                0x002303
Total NVM Capacity:                 512,110,190,592 [512 GB]
Unallocated NVM Capacity:           0
Controller ID:                      1
NVMe Version:                       1.2
Number of Namespaces:               1
Namespace 1 Size/Capacity:          512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002303 561006ea32
Local Time is:                      Thu Dec 22 11:46:02 2022 AEDT
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x001f):   Security Format Frmw_DL NS_Mngmt Self_Test
Optional NVM Commands (0x001f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Log Page Attributes (0x02):         Cmd_Eff_Lg
Maximum Data Transfer Size:         32 Pages
Warning  Comp. Temp. Threshold:     83 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.00W       -        -    0  0  0  0        0       0
 1 +     4.50W       -        -    1  1  1  1        5       5
 2 +     3.00W       -        -    2  2  2  2        5       5
 3 -   0.0700W       -        -    3  3  3  3     1000    5000
 4 -   0.0100W       -        -    4  4  4  4     5000   50000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 -     512       0         1
 1 -    4096       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        42 Celsius
Available Spare:                    100%
Available Spare Threshold:          50%
Percentage Used:                    2%
Data Units Read:                    6,568,038 [3.36 TB]
Data Units Written:                 15,111,742 [7.73 TB]
Host Read Commands:                 164,690,999
Host Write Commands:                338,271,014
Controller Busy Time:               323
Power Cycles:                       904
Power On Hours:                     12
Unsafe Shutdowns:                   305
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               42 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Ok, I rebooted the machine, and the problem with not getting to the login screen seems to have resolved itself. I can now login without resorting to using the grub menu to obtain a console first.

I’ll keep an eye on what happens during the next update, and report back.

Thanks for your help.