View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000365 | AlmaLinux-8 | kernel | public | 2023-01-25 21:26 | 2023-03-28 11:22 |
| Reporter | pascal76 | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | sometimes |
| Status | new | Resolution | open | ||
| OS | almalinux | OS Version | 9 | ||
| Summary | 0000365: warning: %posttrans(kernel-core-5.14.0-162.12.1.el9_1.x86_64) scriptlet failed, exit status 1 | ||||
| Description | On my server: yum reinstall kernel-core-5.14.0-162.12.1.el9_1.x86_64 (same error for yum install) Running transaction Preparing : 1/1 Reinstalling : kernel-core-5.14.0-162.12.1.el9_1.x86_64 1/2 Running scriptlet: kernel-core-5.14.0-162.12.1.el9_1.x86_64 1/2 Running scriptlet: kernel-core-5.14.0-162.12.1.el9_1.x86_64 2/2 Cleanup : kernel-core-5.14.0-162.12.1.el9_1.x86_64 2/2 Running scriptlet: kernel-core-5.14.0-162.12.1.el9_1.x86_64 2/2 dracut: dracut module 'lvm' cannot be found or installed. warning: %posttrans(kernel-core-5.14.0-162.12.1.el9_1.x86_64) scriptlet failed, exit status 1 Error in POSTTRANS scriptlet in rpm package kernel-core Verifying : kernel-core-5.14.0-162.12.1.el9_1.x86_64 1/2 Verifying : kernel-core-5.14.0-162.12.1.el9_1.x86_64 2/2 Reinstalled: kernel-core-5.14.0-162.12.1.el9_1.x86_64 Then: /boot/initramfs-5.14.0-162.12.1.el9_1.x86_64.img is not added and we can't boot anymore (we can't even choose the kernel !) If you reinstall the package and the file already exists, then the scriptlet delete it ! | ||||
| Tags | No tags attached. | ||||
| abrt_hash | |||||
| URL | |||||
|
|
it happened on one of my server only Not on the second one which is similar Not on the 3rd one which has got other hardware |
|
|
it impacts almalinux 9 (sorry it is classified as almalinux 8 and I don't know how to change that) |
|
|
@pascal76 On the server that has the issue, do you have enough space on /boot ? |
|
|
df -h Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur devtmpfs 4,0M 0 4,0M 0% /dev tmpfs 16G 0 16G 0% /dev/shm tmpfs 6,2G 840K 6,2G 1% /run /dev/md126 443G 173G 271G 39% / /dev/md125 200M 7,0M 193M 4% /boot/efi tmpfs 3,1G 0 3,1G 0% /run/user/0 |
|
|
YES ! |
|
|
Do the 2 servers without the issue have the same/similar configuration? |
|
|
in theory yes Same server: https://www.ovhcloud.com/en-gb/bare-metal/advance/adv-3/ About software, here is the diff: rpm -qa > a && ssh bdd2 rpm -qa >> a && cat a | sort | uniq -c |grep -v " 2 " 1 bubblewrap-0.4.1-6.el9.x86_64 1 cabextract-1.9.1-3.el9.x86_64 1 cloud-utils-growpart-0.31-10.el9.x86_64 1 CUnit-2.1.3-25.el9.x86_64 1 device-mapper-multipath-0.8.7-12.el9_1.1.x86_64 1 device-mapper-multipath-libs-0.8.7-12.el9_1.1.x86_64 1 dracut-config-generic-057-13.git20220816.el9.x86_64 1 dracut-config-rescue-057-13.git20220816.el9.x86_64 1 expat-devel-2.4.9-1.el9_1.1.x86_64 1 fwupd-1.7.9-1.el9.alma.1.x86_64 1 glibc-langpack-en-2.34-40.el9_1.1.x86_64 1 glibc-minimal-langpack-2.34-40.el9_1.1.x86_64 1 grub2-pc-2.06-46.el9.alma.x86_64 1 grub2-pc-modules-2.06-46.el9.alma.noarch 1 grub2-tools-efi-2.06-46.el9.alma.x86_64 1 grub2-tools-extra-2.06-46.el9.alma.x86_64 1 iproute-tc-5.18.0-1.el9.x86_64 1 iwl1000-firmware-39.31.5.1-127.el9.noarch 1 iwl100-firmware-39.31.5.1-127.el9.noarch 1 iwl105-firmware-18.168.6.1-127.el9.noarch 1 iwl135-firmware-18.168.6.1-127.el9.noarch 1 iwl2000-firmware-18.168.6.1-127.el9.noarch 1 iwl2030-firmware-18.168.6.1-127.el9.noarch 1 iwl3160-firmware-25.30.13.0-127.el9.noarch 1 iwl5000-firmware-8.83.5.1_1-127.el9.noarch 1 iwl5150-firmware-8.24.2.2-127.el9.noarch 1 iwl6000g2a-firmware-18.168.6.1-127.el9.noarch 1 iwl6050-firmware-41.28.5.1-127.el9.noarch 1 iwl7260-firmware-25.30.13.0-127.el9.noarch 1 json-glib-1.6.6-1.el9.x86_64 1 kernel-5.14.0-162.12.1.el9_1.x86_64 1 kernel-5.14.0-162.6.1.el9_1.x86_64 1 kernel-core-5.14.0-70.30.1.el9_0.x86_64 1 kernel-modules-5.14.0-162.12.1.el9_1.x86_64 1 kernel-modules-5.14.0-162.6.1.el9_1.x86_64 1 langpacks-core-en-3.0-16.el9.noarch 1 langpacks-en-3.0-16.el9.noarch 1 libcap-ng-python3-0.8.2-7.el9.x86_64 1 libevent-devel-2.1.12-6.el9.x86_64 1 libgcab1-1.4-6.el9.x86_64 1 libgusb-0.3.8-1.el9.x86_64 1 libiscsi-1.19.0-5.el9.x86_64 1 libiscsi-utils-1.19.0-5.el9.x86_64 1 libjcat-0.1.6-3.el9.x86_64 1 librdmacm-41.0-3.el9.x86_64 1 libsmbios-2.4.3-4.el9.x86_64 1 libusbx-1.0.26-1.el9.x86_64 1 libxmlb-0.3.3-1.el9.x86_64 1 linux-firmware-20220708-127.el9.noarch 1 mokutil-0.4.0-9.el9.x86_64 1 NetworkManager-config-server-1.40.0-1.el9.noarch 1 nodejs-16.18.1-3.el9_1.x86_64 1 nodejs-docs-16.18.1-3.el9_1.noarch 1 nodejs-full-i18n-16.18.1-3.el9_1.x86_64 1 nodejs-libs-16.18.1-3.el9_1.x86_64 1 npm-8.19.2-1.16.18.1.3.el9_1.x86_64 1 openssl-devel-3.0.1-43.el9_0.x86_64 1 python-unversioned-command-3.9.14-1.el9_1.1.noarch 1 qemu-guest-agent-7.0.0-13.el9.x86_64 1 shim-x64-15.6-1.el9.alma.x86_64 1 systemd-devel-250-12.el9_1.1.x86_64 1 tcpdump-4.99.0-6.el9.x86_64 It should be the same but I think I installed the first server (not impacted) differently Is it possibile to have the (debug) logs of "scriptlet failed, exit status 1" ? |
|
|
I'm interested in the size of /boot. You don't seem to have /boot but only /boot/efi. There are some reports that indicate 200M is not enough for /boot/efi. So wondered if the 2 "good" servers have a larger size. |
|
|
server 1: Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/md125 201M 7,0M 194M 4% /boot/efi dev server: Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/md125 200M 7,0M 193M 4% /boot/efi du -hsc /boot 240M /boot on dev and server1 107M on the impacted server |
|
|
> 240M /boot on dev and server1 > 107M on the impacted server It's less on the server that fails? Anyway the links I looked at were (FYI): https://bugzilla.redhat.com/show_bug.cgi?id=1844423 "Bug 1844423 - /boot size 200Mib is not enough " https://ask.fedoraproject.org/t/f36-kernel-wont-install-due-to-running-out-of-space-in-boot-efi/22498 "F36 kernel won’t install due to running out of space in /boot/efi" |
|
|
>It's less on the server that fails? Yes, because the server is more recent There are less kernels on it |
|
|
sorry the space size of the faulty server was incorrect (I gave the data from the dev server ...) Filesystem Size Used Avail Use% Mounted on devtmpfs 4,0M 0 4,0M 0% /dev tmpfs 63G 0 63G 0% /dev/shm tmpfs 26G 50M 26G 1% /run /dev/md126 863G 53G 810G 7% / /dev/md127 1016M 138M 878M 14% /boot /dev/nvme0n1p1 511M 2,5M 509M 1% /boot/efi |
|
|
The bug : it was due to this file from OVH ... /etc/dracut.conf.d/98-ovh.conf logfile=/var/log/dracut.log fileloglvl=6 add_dracutmodules+=" lvm mdraid " add_drivers+=" 8139too e1000 e1000e igb r8169 dm-raid raid0 raid1 raid10 raid456 mlx4_en mptspi mptsas ixgbe nvme " hostonly="yes" |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-01-25 21:26 | pascal76 | New Issue | |
| 2023-01-25 21:27 | pascal76 | Note Added: 0000796 | |
| 2023-01-26 09:40 | pascal76 | Note Added: 0000797 | |
| 2023-01-27 18:08 | toracat | Note Added: 0000798 | |
| 2023-01-27 18:09 | pascal76 | Note Added: 0000799 | |
| 2023-01-27 18:09 | pascal76 | Note Added: 0000800 | |
| 2023-01-27 18:20 | toracat | Note Added: 0000801 | |
| 2023-01-27 18:27 | pascal76 | Note Added: 0000802 | |
| 2023-01-27 18:33 | toracat | Note Added: 0000803 | |
| 2023-01-27 18:39 | pascal76 | Note Added: 0000804 | |
| 2023-01-27 19:02 | toracat | Note Added: 0000805 | |
| 2023-01-27 19:13 | pascal76 | Note Added: 0000806 | |
| 2023-01-27 19:17 | pascal76 | Note Added: 0000807 | |
| 2023-03-28 11:22 | pascal76 | Note Added: 0000844 |
