Subject: depmod: WARNING: could not open modules.builtin.modinfo at /lib/modules/4.19.176-0-vanilla error

From: Amey <[email-masked]>
Date: Thu, 29 Aug 2024 17:22:20 +0200

I did Alpine upgrade from 3.19.x to 3.20.2 in my physical server using
an upgrade shell script.

Repositories under /etc/apk dir =
http://dl-4.alpinelinux.org/alpine/v3.19/main
http://dl-4.alpinelinux.org/alpine/v3.19/community
https://dl-cdn.alpinelinux.org/alpine/v3.20/main/
https://dl-cdn.alpinelinux.org/alpine/v3.20/community/

After upgrade, I see following messages at end =

(247/249) Upgrading xxd (9.0.2127-r0 -> 9.1.0414-r0)
(248/249) Upgrading vim (9.0.2127-r0 -> 9.1.0414-r0)
(249/249) Purging argon2-libs (20190702-r5)
Executing busybox-1.36.1-r29.trigger
Executing ca-certificates-20240705-r0.trigger
Executing kmod-32-r0.trigger
depmod: WARNING: could not open modules.builtin.modinfo at
/lib/modules/4.19.176-0-vanilla: No such file or directory
Executing mkinitfs-3.10.1-r0.trigger
==> initramfs: creating /boot/initramfs-vanilla for 4.19.176-0-vanilla
depmod: WARNING: could not open modules.builtin.modinfo at
/tmp/mkinitfs.eJmnnk/lib/modules/4.19.176-0-vanilla: No such file or
directory
OK: 1896 MiB in 301 packages
OK: 1896 MiB in 301 packages
OK: 1896 MiB in 301 packages

If I do cat /etc/os-release =
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.20.2
PRETTY_NAME="Alpine Linux v3.20"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"

output / ls of /lib/modules = 4.19.176-0-vanilla

I am now worried if the OS fails to boot after the restart/reboot.
Any thoughts if I can ignore that warning and reboot the server?
The OS has been upgraded to 3.19 version earlier from older versions.

Regards,
Amey.

---

From: Konstantin Kulikov <[email-masked]>
Date: Fri, 30 Aug 2024 23:12:58 +0300

Kernel you are using was removed 5 years ago
https://git.alpinelinux.org/aports/commit/?id=eba4f554cc5

1. remove all repos from /etc/apk/repositories, except 3.20 ones.
2. apk update
3. apk upgrade --available --simulate
4. carefully check what packages are missing and what needs reinstalling
5. install linux-lts and whatever else
6. check that bootloader picked up new kernel

---

From: Amey <[email-masked]>
Date: Mon, 2 Sep 2024 08:24:44 +0200

Hello Konstantin,

Thank you very much for your input.

> 1. remove all repos from /etc/apk/repositories, except 3.20 ones.
Done.
> 2. apk update
Done
> 3. apk upgrade --available --simulate
Output =
apk upgrade --available --simulate
(1/48) Replacing acct (6.6.4-r2 -> 6.6.4-r2)
(2/48) Replacing acct-openrc (6.6.4-r2 -> 6.6.4-r2)
(3/48) Replacing alpine-keys (2.4-r1 -> 2.4-r1)
(4/48) Replacing apk-tools (2.14.4-r0 -> 2.14.4-r0)
(5/48) Replacing scanelf (1.3.7-r2 -> 1.3.7-r2)
(6/48) Replacing nettle (3.9.1-r0 -> 3.9.1-r0)
(7/48) Replacing libtasn1 (4.19.0-r2 -> 4.19.0-r2)
(8/48) Replacing chrony (4.5-r0 -> 4.5-r0)
(9/48) Replacing chrony-openrc (4.5-r0 -> 4.5-r0)
(10/48) Upgrading libcurl (8.9.1-r0 -> 8.9.1-r1)
(11/48) Upgrading curl (8.9.1-r0 -> 8.9.1-r1)
(12/48) Replacing pcre (8.45-r3 -> 8.45-r3)
(13/48) Replacing libmnl (1.0.5-r2 -> 1.0.5-r2)
(14/48) Replacing libnftnl (1.2.6-r0 -> 1.2.6-r0)
(15/48) Replacing libxtables (1.8.10-r3 -> 1.8.10-r3)
(16/48) Replacing iptables (1.8.10-r3 -> 1.8.10-r3)
(17/48) Replacing iptables-openrc (1.8.10-r3 -> 1.8.10-r3)
(18/48) Replacing tar (1.35-r2 -> 1.35-r2)
(19/48) Replacing libbz2 (1.0.8-r6 -> 1.0.8-r6)
(20/48) Replacing libmd (1.1.0-r0 -> 1.1.0-r0)
(21/48) Replacing libcom_err (1.47.0-r5 -> 1.47.0-r5)
(22/48) Replacing e2fsprogs-libs (1.47.0-r5 -> 1.47.0-r5)
(23/48) Replacing e2fsprogs (1.47.0-r5 -> 1.47.0-r5)
(24/48) Replacing jansson (2.14-r4 -> 2.14-r4)
(25/48) Replacing isl26 (0.26-r1 -> 0.26-r1)
(26/48) Replacing mpfr4 (4.2.1-r0 -> 4.2.1-r0)
(27/48) Replacing mpc1 (1.3.1-r1 -> 1.3.1-r1)
(28/48) Replacing libip4tc (1.8.10-r3 -> 1.8.10-r3)
(29/48) Replacing libip6tc (1.8.10-r3 -> 1.8.10-r3)
(30/48) Replacing iptables-legacy (1.8.10-r3 -> 1.8.10-r3)
(31/48) Replacing lddtree (1.27-r0 -> 1.27-r0)
(32/48) Replacing json-c (0.17-r0 -> 0.17-r0)
(33/48) Replacing make (4.4.1-r2 -> 4.4.1-r2)
(34/48) Replacing mii-tool (2.10-r3 -> 2.10-r3)
(35/48) Replacing net-tools (2.10-r3 -> 2.10-r3)
(36/48) Replacing libtirpc-conf (1.3.4-r0 -> 1.3.4-r0)
(37/48) Replacing libtirpc-nokrb (1.3.4-r0 -> 1.3.4-r0)
(38/48) Replacing libexpat (2.6.2-r0 -> 2.6.2-r0)
(39/48) Replacing gdbm (1.23-r1 -> 1.23-r1)
(40/48) Replacing lz4-libs (1.9.4-r5 -> 1.9.4-r5)
(41/48) Replacing popt (1.19-r3 -> 1.19-r3)
(42/48) Replacing libxxhash (0.8.2-r2 -> 0.8.2-r2)
(43/48) Replacing libutempter (1.2.1-r9 -> 1.2.1-r9)
(44/48) Replacing screen (4.9.1-r1 -> 4.9.1-r1)
(45/48) Replacing mtools (4.0.43-r1 -> 4.0.43-r1)
(46/48) Replacing syslinux (6.04_pre1-r15 -> 6.04_pre1-r15)
(47/48) Replacing libpcap (1.10.4-r1 -> 1.10.4-r1)
(48/48) Replacing tcpdump (4.99.4-r1 -> 4.99.4-r1)
OK: 1896 MiB in 301 packages

> 4. carefully check what packages are missing and what needs reinstalling
I think I'll update all packages as all of them look essential packages.

> 5. install linux-lts and whatever else
May I know how can I do that? Thanks.

> 6. check that bootloader picked up new kernel
Yes will do.