Bug#1114894: OS-Prober generates not running entries for Debian 12

Debian debian at decotrain.de
Fri Sep 12 10:04:51 BST 2025


Am 11.09.25 um 13:38 schrieb Pascal Hambourg:
> On 11/09/2025 at 11:50, Debian wrote:
>>
>> this entry is generated, that ends somehow in a shell without 
>> starting the graphical interface
>
> What kind of shell ? grub shell, initramfs shell, emergency shell, 
> login prompt ?

As I can remember it was a regular login prompt and not a emergency shell.
I did wonder why the graphical interface did not start.

>
>>          linux /vmlinuz root=/dev/sda2
>>          initrd /initrd.img
>
> Is it the exact generated entry ?
Yes - look above for the generated part of the grub.cfg.
> What is the output of linux-boot-prober /dev/sda2 (or whatever the 
> correct partition is) ?

# linux-boot-prober /dev/sdb2
/dev/sdb2:/dev/sdb2::/vmlinuz:/initrd.img:root=/dev/sdb2
/dev/sdb2:/dev/sdb2::/vmlinuz:/initrd.img:root=/dev/sdb2
/dev/sdb2:/dev/sdb2::/vmlinuz:/initrd.img.old:root=/dev/sdb2
/dev/sdb2:/dev/sdb2::/boot/vmlinuz-6.1.0-39-amd64:/boot/initrd.img-6.1.0-39-amd64:root=/dev/sdb2
/dev/sdb2:/dev/sdb2::/vmlinuz.old:/initrd.img.old:root=/dev/sdb2
/dev/sdb2:/dev/sdb2::/vmlinuz:/initrd.img:root=/dev/sdb2
/dev/sdb2:/dev/sdb2::/vmlinuz:/initrd.img:root=/dev/sdb2
/dev/sdb2:/dev/sdb2::/vmlinuz:/initrd.img.old:root=/dev/sdb2

# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0   1,8T  0 disk
├─sda1   8:1    0    10G  0 part
├─sda2   8:2    0    40G  0 part
├─sda3   8:3    0    40G  0 part
├─sda4   8:4    0     1K  0 part
├─sda5   8:5    0   256M  0 part [SWAP]
├─sda6   8:6    0    40G  0 part /ext
└─sda7   8:7    0   1,7T  0 part /srv
sdb      8:16   0 223,6G  0 disk
├─sdb1   8:17   0    50G  0 part
├─sdb2   8:18   0    50G  0 part
├─sdb3   8:19   0    50G  0 part
├─sdb4   8:20   0     1K  0 part
├─sdb5   8:21   0    40G  0 part /
└─sdb6   8:22   0  33,6G  0 part
sdc      8:32   1     0B  0 disk
sr0     11:0    1  1024M  0 rom


> Incomplete entries with root=/dev/sd* instead of root=UUID can be 
> generated if /boot/grub/grub.cfg is missing in the foreign system. But 
> /vmlinuz is usually a symlink and linux-boot-prober fallback script 
> should ignore symlinks.
The error occurs after the upgrade when grub has been installed in 
Debian 13.
>
>
>> The grub.cfg has been edited manually now and then it works for all 
>> different OS-versions.
>
> Is this the edited menu entry ?
No - it is the one above with the UUID that works.
>
>>      linux /boot/vmlinuz-6.1.0-39-amd64 root=/dev/sdb2
>>      initrd /boot/initrd.img-6.1.0-39-amd64
>



More information about the Pkg-grub-devel mailing list