I have run an apt-dist upgrade on my dedicated server that uses a
kernel from the provider (OVH) and I am getting the following
MTL ➜ ~ apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/10.5 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 61164 files and directories currently installed.)
Preparing to unpack .../ovhkernel-4.9-xxxx-std-ipv6-image_4.9.159-599550_amd64.deb ...
Unpacking ovhkernel-4.9-xxxx-std-ipv6-image (4.9.159-599550) over (4.9.158-590910) ...
Setting up ovhkernel-4.9-xxxx-std-ipv6-image (4.9.159-599550) ...
update-initramfs: Generating /boot/initrd.img-4.9.159-xxxx-std-ipv6-64
WARNING: missing /lib/modules/4.9.159-xxxx-std-ipv6-64
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.9.159-xxxx-std-ipv6-64: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_SUPVlB/lib/modules/4.9.159-xxxx-std-ipv6-64/modules.order: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_SUPVlB/lib/modules/4.9.159-xxxx-std-ipv6-64/modules.builtin: No such file or directory
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.9.159-xxxx-std-ipv6-64
Found initrd image: /boot/initrd.img-4.9.159-xxxx-std-ipv6-64
Adding boot menu entry for EFI firmware configuration
I am concerned that this could cause the machine not to boot
anymore but I see that the grub config file has been created and
installed. Is it anything to worry about? I cannot understand as I
have another dedicated server with exactly the same config with
the same provider and it has no issues.