| tempforever | I've got a buster->beowulf->chimaera->daedalus installation, rebooted after each migration/dist-upgrade stage. It has kernel 6.1.0-26 installed, but it keeps booting into 4.19.0-25 (from buster/beowulf). Any idea why it won't boot to the newer kernel, what things I can check? | 18:21 |
|---|---|---|
| tempforever | If it matters (and it may) this is a VPS. I have another one with the same company that does boot the 6.1 kernel. | 18:26 |
| rwp | tempforever, It's a VPS? Does the 4.19.0-25 kernel still exist on the system? Or is it the hosting that is booting that kernel from elsewhere/ | 18:38 |
| rwp | *elsewhere? It is possible for the VPS hosting to force booting a specific kernel. Linode has an option to do that for example. | 18:39 |
| rwp | However when Linode does that it is one of the very latest kernels. | 18:39 |
| rwp | Also, if you are using the symlinks to boot then check that they are updating correctly. (I don't use the symlinks.) ls -l / | 18:39 |
| rwp | Check this, if it exists: grep do_symlinks /etc/kernel-img.conf | 18:40 |
| rwp | And also related: grep link_in_boot /etc/kernel-img.conf | 18:40 |
| tempforever | the 4.19 kernel exists in /boot and is a warning when I try to remove it, as it's the kernel in use | 18:40 |
| rwp | Is it booting from /vmlinuz -> boot/vmlinuz-4.19.0-25-amd64 something something there because the symlink was not updated? | 18:41 |
| tempforever | /etc/kernel-img.conf : do_symlinks = yes | 18:42 |
| tempforever | link_in_boot = no | 18:43 |
| rwp | It's the linux-update-symlinks command which is called by the package to update those symlinks. I have seen systems where it thought they were manually overridden and therefore it intentionally avoided updating the symlinks. They needed to be manually updated in order to get moving forward again. | 18:43 |
| rwp | Also, ensure you have "linux-image-amd64" package installed as that is the package that is upgraded and pulls in the newer kernel packages. | 18:44 |
| tempforever | /initrd.img -> boot/initrd.img-6.1.0-26-amd64 /vmlinux also points to 6.1 | 18:44 |
| tempforever | linux-image-amd64: Installed: 6.1.112-1 | 18:45 |
| rwp | Hmm... Deeper digging then, I would run "update-grub" manually and see what output it prints out. | 18:45 |
| rwp | Example output from an Unstable system: https://paste.debian.net/plain/1333333 | 18:46 |
| tempforever | I actually just tried that (update-grub) and rebooted. it finds both 6.1 and 4.19 (in that order) | 18:46 |
| rwp | The result of that is the /boot/grub/grub.cfg file. You would browse that file and verify the result. | 18:46 |
| rwp | Double check /etc/default/grub and look for the GRUB_DEFAULT=0 line. That's the default booting kernel in the array booting entry 0 the first kernel. If it says GRUB_DEFAULT=1 then it would boot the 2nd kernel. | 18:47 |
| tempforever | GRUB_DEFAULT=0 | 18:48 |
| rwp | Hmm... Verify that in the /boot/grub/grub.cfg file that the first entry really is the new kernel. Look for the first "linux/vmlinuz-....." line. | 18:49 |
| tempforever | there is no /boot/grub/grub.cfg. there is a /boot/grub2/grub.cfg (dated 10/6/2022) which is odd since grub2 is not installed. | 18:49 |
| tempforever | oh, that grub2/grub.cfg is a symlink to grub/menu.lst | 18:49 |
| rwp | /boot/grub2/?? I know you started with buster->beowulf->chimaera->daedalus but my systems with exactly the same path have /boot/grub/ there. Hmm... | 18:50 |
| tempforever | that's the only file in "grub2" the rest are in "grub" | 18:50 |
| rwp | menu.lst is GRUB v1 not GRUB2. | 18:50 |
| rwp | I must assume that /boot/grub2/ is just there on disk and not used. Since it seems to be nonsense there. Check /boot/grub/ for the grub.cfg file. | 18:51 |
| rwp | I am heading AFK for some time. Good luck! | 18:53 |
| tempforever | menu.lst only contains 4.19 even though update-grub lists both 6.1 and 4.19, so I think we found the problem | 18:53 |
| tempforever | I'm going to compare my other working grub config with this one | 18:54 |
| tempforever | OK I basically copied the grub.cfg from the 6.1-working-vps to the 4.19-stuck-vps, edited it and rebooted, it's now running 6.1 kernel | 19:09 |
| tempforever | not grub.cfg, it was menu.lst | 19:11 |
| tempforever | Thanks for your help | 19:15 |
| rwp | That feels strange to me that menu.lst is being used at all in this current time. I feel this is something particular to this VPS provider. (I am a quick on and off the keyboard and now gone again.) | 20:04 |
| fsmithred | grub-legacy still exists, even in ceres. | 20:23 |
| fsmithred | and still hasn't reached version 1.0 | 20:23 |
| tempforever | yeah this is using grub-legacy | 21:24 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!