You just have to ask them for their documentation about their VPS, and in particular the boot loader, since you’ve got security issue to deal with.
1 Like
Just tell them what you are trying to do
1 Like
Same thing here.
No update aviable in Yunohost console admin. No update with APT.
dpkg -l | grep linux-image :
rc linux-image-4.19.0-16-amd64 4.19.181-1 amd64 Linux 4.19 for 64-bit PCs (signed)
rc linux-image-4.19.0-21-amd64 4.19.249-2 amd64 Linux 4.19 for 64-bit PCs (signed)
rc linux-image-5.10.0-17-amd64 5.10.136-1 amd64 Linux 5.10 for 64-bit PCs (signed)
rc linux-image-5.10.0-18-amd64 5.10.140-1 amd64 Linux 5.10 for 64-bit PCs (signed)
rc linux-image-5.10.0-19-amd64 5.10.149-2 amd64 Linux 5.10 for 64-bit PCs (signed)
rc linux-image-5.10.0-20-amd64 5.10.158-2 amd64 Linux 5.10 for 64-bit PCs (signed)
ii linux-image-5.10.0-21-amd64 5.10.162-1 amd64 Linux 5.10 for 64-bit PCs (signed)
rc linux-image-amd64 5.10.162-1 amd64 Linux for 64-bit PCs (meta-package)
cat /boot/grub/grub.cfg :
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
search --no-floppy --fs-uuid --set=root e0513575-0531-49a5-a5e4-99b2ab8357c5
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=fr_FR
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e0513575-0531-49a5-a5e4-99b2ab8357c5' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
search --no-floppy --fs-uuid --set=root 21636fda-1ec8-4575-966e-cc91cfc219fb
echo 'Loading Linux 5.10.0-21-amd64 ...'
linux /vmlinuz-5.10.0-21-amd64 root=UUID=e0513575-0531-49a5-a5e4-99b2ab8357c5 ro quiet
echo 'Loading initial ramdisk ...'
initrd /initrd.img-5.10.0-21-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-e0513575-0531-49a5-a5e4-99b2ab8357c5' {
menuentry 'Debian GNU/Linux, with Linux 5.10.0-21-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-21-amd64-advanced-e0513575-0531-49a5-a5e4-99b2ab8357c5' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
search --no-floppy --fs-uuid --set=root 21636fda-1ec8-4575-966e-cc91cfc219fb
echo 'Loading Linux 5.10.0-21-amd64 ...'
linux /vmlinuz-5.10.0-21-amd64 root=UUID=e0513575-0531-49a5-a5e4-99b2ab8357c5 ro quiet
echo 'Loading initial ramdisk ...'
initrd /initrd.img-5.10.0-21-amd64
}
menuentry 'Debian GNU/Linux, with Linux 5.10.0-21-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-21-amd64-recovery-e0513575-0531-49a5-a5e4-99b2ab8357c5' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
search --no-floppy --fs-uuid --set=root 21636fda-1ec8-4575-966e-cc91cfc219fb
echo 'Loading Linux 5.10.0-21-amd64 ...'
linux /vmlinuz-5.10.0-21-amd64 root=UUID=e0513575-0531-49a5-a5e4-99b2ab8357c5 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-5.10.0-21-amd64
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###
ls -la /etc/grub.d/
total 100
drwxr-xr-x 2 root root 4096 16 mai 17:30 .
drwxr-xr-x 121 root root 12288 29 mai 12:13 ..
-rwxr-xr-x 1 root root 10046 11 juil. 2021 00_header
-rwxr-xr-x 1 root root 6260 11 juil. 2021 05_debian_theme
-rwxr-xr-x 1 root root 14123 15 sept. 2022 10_linux
-rwxr-xr-x 1 root root 14180 15 sept. 2022 20_linux_xen
-rwxr-xr-x 1 root root 12923 2 oct. 2023 30_os-prober
-rwxr-xr-x 1 root root 1372 15 sept. 2022 30_uefi-firmware
-rwxr-xr-x 1 root root 214 1 mars 2021 40_custom
-rwxr-xr-x 1 root root 215 15 sept. 2022 41_custom
-rw-r--r-- 1 root root 483 1 mars 2021 README
ls /boot/vmlinuz-* /boot/kernel-*
ls: impossible d'accéder à '/boot/kernel-*': Aucun fichier ou dossier de ce type
/boot/vmlinuz-5.10.0-21-amd64
uname -a :
Linux 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux
sudo apt dist-upgrade :
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Calcul de la mise à jour... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
N: « php.list.old » dans le répertoire « /etc/apt/sources.list.d/ » a été ignoré car il utilise une extension non valable
admin@wellby:/etc/apt$ sudo apt dist-upgrade
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
Calcul de la mise à jour... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
N: « php.list.old » dans le répertoire « /etc/apt/sources.list.d/ » a été ignoré car il utilise une extension non valable
cat /etc/debian_version : 12.14
cat /etc/apt/sources.list :
# deb cdrom:[Debian GNU/Linux 10 _Buster_ - Unofficial amd64 CD Binary-1 20210504-19:05]/ bookworm main non-free non-free-firmware
#deb cdrom:[Debian GNU/Linux 10 _Buster_ - Unofficial amd64 CD Binary-1 20210504-19:05]/ bookworm main non-free non-free-firmware
deb http://ftp.debian.org/debian` bookworm main contrib deb-src http://ftp.debian.org/debian bookworm main contrib non-free-firmware`
## YunoHost repository
deb [signed-by=/usr/share/keyrings/yunohost-bookworm.gpg] http://forge.yunohost.org/debian/` bookworm stable deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware`
deb http://security.debian.org/debian-security` bookworm-security main contrib non-free non-free-firmware deb-src http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware`
# bookworm-updates, previously known as 'volatile'
deb http://ftp.debian.org/debian` bookworm-updates main contrib non-free non-free-firmware deb-src http://ftp.debian.org/debian bookworm-updates main contrib non-free non-free-firmware`
Very strange issue.
Hello Dr.Wily ! It’s absolutely not the same issue, since you’ve got a grub.cfg file.
So please, could you :
- Create a new issue
- erase your post in this issue
- use yunopaste instead of putting all the text in the post
It will be easier for everyone to help each other.
-
I don’t have a file at /boot/grub/grub.cfg
-
ls -la /etc/grub.d/
ls: cannot access ‘/etc/grub.d/’: No such file or directory -
ls /boot/vmlinuz-* /boot/kernel-*
ls: cannot access ‘/boot/kernel-*’: No such file or directory
/boot/vmlinuz-5.10.0-28-amd64 /boot/vmlinuz-6.1.0-49-amd64
@elgee : what did the support tells you ?
I am sorry, I thought the above-quoted message was a new one. That is why I replied to it. I will contact the VPS provider and see if I can get them to point me to the locations of the necessary files/directories.
I am yet to write to them. Hopefully I’ll be able to do it within the next 24 hours.
1 Like
Hello all,
I have drafted the following email to the VPS provider. Can you please take a look at it and tell me if I am asking the right question:
Hello, I began using this VPS provided by 1984 few years ago. I run a Debian based server distro installed on top of the Debian installation I did using the disk image provided by you. I started with Debian 11, and now I am on Debian 12.
May I know if the Debian disk images you provide use a custom location for the bootloader? The reason I am asking this is explained below:
Last week, in the light of copy.fail exploit, I was trying to make sure that I am running the latest, patched Linux kernel against it. I noticed that I have two different kernels installed. I wanted to switch to the newest and up-to-date version of the kernel by changing the bootloader settings. Only then I found out that the grub/bootloader configurations cannot be found in the usual/default locations. Please let me know where can I find the relevant configuration files.
Thanks very much for your excellent support over the years!
I ended up sending the above email to them. I got the following reply:
You have a type of VPS that loads the kernel from directory on the host. After you upgrade you should shutdown your server and then run it from the CP. When it starts the system will check the latest kernel you have installed and set the host kernel to mirror that. Try it out. Then run the demo exploit and if it is still vulnerable I will take a closer look at this.
That is a lot to digest. I am sharing it here hoping some of you guys might have helpful pointers.
He is just telling you that the system has no bootloader. 
You should try to shutdown your server, and then, through the control panel, you start your server (as a reboot).
Do you have many users using your server ?
If not, or not at that time, let’s do it !
I tried this a couple of times. But there is no way to make it use the new kernel. I am still using the older version.
It looks like the only option I have is removing the old version and hoping for the best that the system will start using the new version after the reboot.
Humm … not sure.
Please consider asking support for help, cause after many reboot, the only kernel that is loaded is the old one.
There is a 6.1.172 kernel, and the bootloader still uses the 5.10.0.28
At the moment, I see that you have many old linux images, like the 4.x => I think you could delete those ones.
1 Like
Run a regeneration of apt yunohost tools regen-conf apt -f
Then rerun apt update
This is clearly a matter related to your VPS provider.
this is interesting but still does not tell how the kernel is chosen, what exact filename is got and what kernel options are passed one.
here we have /boot/vmlinuz-5.10.0-28-amd64 /boot/vmlinuz-6.1.0-49-amd64
but i think the default might be this with pointed by symbolic link (/vmlinux if it exists.
ls -l /vmlinuz*
and what is /boot ?
mount | grep boot
If i spotted it right from your mail their wiki is start [Viskubrunnur 1984] .
They seems to have very few information on their wiki about anything related to linux custom image .
Do they provide snapshots ? if yes you might do one snaphsot now, then tweaking your system until you get it working will be a matter of restoring snapshot if it fails…
1 Like
ls -l /vmlinuz*
lrwxrwxrwx 1 root root 27 May 28 10:51 /vmlinuz → boot/vmlinuz-6.1.0-49-amd64
lrwxrwxrwx 1 root root 28 May 29 06:21 /vmlinuz.old → boot/vmlinuz-5.10.0-28-amd64
This doesn’t give any output at all.
Yes, they do have snapshots. I have taken one, vaguely thinking that I’ll remove the older kernel and see if the system automatically takes the next available one. But I still could not make up my mind to do that
This didn’t change the situation. I didn’t get any new updates. The older kernel is still in use.
Okay, I went ahead and removed the following. The output is reassuring!
sudo apt remove linux-image-5.10.0-28-amd64
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
linux-image-5.10.0-28-amd64
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 318 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database … 74547 files and directories currently installed.)
Removing linux-image-5.10.0-28-amd64 (5.10.209-2) …
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-49-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-49-amd64
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.10.0-28-amd64
Going to reboot now. Wish me luck!
It worked! The new kernel is in use now!
uname -a
Linux alochana.net 6.1.0-49-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 (2026-05-26) x86_64 GNU/Linux
Thanks very much for all the helpful advise and pointers! 
5 Likes