Am 14.09.25 um 20:41 schrieb Pascal Hambourg:
What's about this two lines?linux /boot/vmlinuz-6.1.0-39-amd64 root=/dev/sdb2 initrd /boot/initrd.img-6.1.0-39-amd64They do not match "linux /vmlinuz root=/dev/sda2" in any way: the kernel and initramfs pathnames and the root device are different.
That's the reason for this bug report. :-) This has been generated by the scripts from grub.
Ideally, linux-boot-prober collects menu entry information (entry label, kernel path and parameters...) from grub.cfg when it is present.
Why this?So there is placed a wrong UUID grabbed from scripts even it is read from the correct partition.
Now it is not surprising that there is so much chaos in the generation of the files, when someone works with much different OS in different partititons. The other versions of OS will not update the grub.cfg when there is no upgrade that calls the update-grub.
I copied your Debian 12 grub.cfg to a test partition and linux-boot-prober and os-prober generate the expected kernel command line.I can only say that the update-grub scripts don't work for me, because there are many boot partitions and I am cloning versions of an OS to work with.Maybe there are some leftovers from previous versions which cause this. I still cannot figure out how linux-boot-prober /dev/sdb2 could possibly generate the lines your reported in you previous post. While or after running it, could you check its debug logs in the system logs (in /var/log/syslog or with journalctl depending on which logging daemon you have) ?
A new update-grub is called in Debian 13 and the syslog output is attached. Hopefully this will help.
update-grub-syslog.txt.gz
Description: application/gzip
