7.4-17 with memtest86 to 8.1.4 upgrade hangs at configure

[francoisd]

In place upgrade of 7.4-17 with memtest86 installed to 8.1.4 hangs at

Unpacking zfs-zed (2.2.2-pve1) over (2.1.14-pve1) ...
Setting up memtest86+ (6.10-4) ...
Installing new version of config file /etc/grub.d/20_memtest86+ ...

root@pve3:~# ps -ef | rg '\bmemtest'
root      412929  412928  0 12:14 pts/1    00:00:00 /bin/sh /var/lib/dpkg/info/memtest86+.postinst configure 5.01-3.1
root@pve3:~# strace -p 412929
strace: Process 412929 attached
wait4(-1,

My workaround was just to kill (TERM) it:

root@pve3:~# kill 412929

 

[francoisd]

Another hang a bit later makes me thing something might be wrong with my system:

Setting up proxmox-kernel-6.5.11-8-pve-signed (6.5.11-8) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.5.11-8-pve /boot/vmlinuz-6.5.11-8-pve
update-initramfs: Generating /boot/initrd.img-6.5.11-8-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.5.11-8-pve /boot/vmlinuz-6.5.11-8-pve
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 6.5.11-8-pve /boot/vmlinuz-6.5.11-8-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.5.11-8-pve /boot/vmlinuz-6.5.11-8-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.5.11-8-pve /boot/vmlinuz-6.5.11-8-pve

After digging in the stopped process, I have:

root@pve3:~# strace -p 434895
strace: Process 434895 attached
read(3, ^Cstrace: Process 434895 detached
 <detached ...>

root@pve3:~# lsof | rg 434895
grub-mkco 434895                          root  cwd       DIR              253,1     4096          2 /
grub-mkco 434895                          root  rtd       DIR              253,1     4096          2 /
grub-mkco 434895                          root  txt       REG              253,1   125640     262207 /usr/bin/dash
grub-mkco 434895                          root  mem       REG              253,1  1922136     263141 /usr/lib/x86_64-linux-gnu/libc.so.
6
grub-mkco 434895                          root  mem       REG              253,1   210968     262837 /usr/lib/x86_64-linux-gnu/ld-linux
-x86-64.so.2
grub-mkco 434895                          root    0u      CHR              136,1      0t0          4 /dev/pts/1
grub-mkco 434895                          root    1u      CHR              136,1      0t0          4 /dev/pts/1
grub-mkco 434895                          root    2u      CHR              136,1      0t0          4 /dev/pts/1
grub-mkco 434895                          root    3r     FIFO               0,13      0t0    2021869 pipe
grub-mkco 434895                          root   10r      REG              253,1     8657     265624 /usr/sbin/grub-mkconfig

Again, I released the lock by killing the process.

I ended up with:

Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
Processing triggers for rsyslog (8.2302.0-1) ...
Errors were encountered while processing:
 memtest86+
 proxmox-kernel-6.5.11-8-pve-signed
 proxmox-kernel-6.5
 proxmox-default-kernel
 proxmox-ve
 dmeventd
 lvm2
 grub-pc
 libpve-storage-perl
 ceph-volume
 pve-container
 pve-manager
 qemu-server
 libpve-guest-common-perl
 pve-ha-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
W: Operation was interrupted before it could finish

Hopefully removing the memtest86+ package and some other packages did not hang and re-run the above configs.

apt remove memtest86+
apt autoremove

I have no clue it comes from memtest86+. Just leaving in the forum if someone else encounters the same behavior.