Am 13.09.25 um 15:49 schrieb Pascal Hambourg:
Copied from the initial report:Again, I do not see any line "linux /vmlinuz root=/dev/sda2" here.
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-amd64 Both files originally generated by update-grub are attached now.
Can you attach the full contents of /boot/grub/grub.cfg in Debian 12 root filesytem ?This is a bug for Debian 13 and not for Debian 12.This could be a bug in parsing menu entries from the foreign grub.cfg.
O.K. I have no idea where the informations are collected from.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.
How was I supposed to know about that ?
Sorry - we talk past each other.
It was not easy to boot the copy in /dev/sdb5If you used os-prober to generate menu entries for the copy, the grub.cfg copy originally contained the wrong UUID in the kernel command line and os-prober imported them, so the generated menu entries actually mounted the original root partition.
Yes - that's the reason it must be edited manually.
grub.cfg.13.gz
Description: application/gzip
grub.cfg.12.gz
Description: application/gzip
