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/mainhttp://dl-4.alpinelinux.org/alpine/v3.19/communityhttps://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.
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