Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1260947 > unrolled thread

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

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1114894: OS-Prober generates not running entries for Debian 12 Debian <debian@decotrain.de> - 2025-09-11 12:40 +0200
    Bug#1114894: OS-Prober generates not running entries for Debian 12 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2025-09-11 13:50 +0200
      Bug#1114894: OS-Prober generates not running entries for Debian 12 Debian <debian@decotrain.de> - 2025-09-12 11:40 +0200
        Bug#1114894: OS-Prober generates not running entries for Debian 12 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2025-09-13 11:00 +0200
      Bug#1114894: OS-Prober generates not running entries for Debian 12 Debian <debian@decotrain.de> - 2025-09-13 13:40 +0200
        Bug#1114894: OS-Prober generates not running entries for Debian 12 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2025-09-13 16:00 +0200
          Bug#1114894: OS-Prober generates not running entries for Debian 12 Debian <debian@decotrain.de> - 2025-09-14 10:10 +0200
            Bug#1114894: OS-Prober generates not running entries for Debian 12 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2025-09-14 20:50 +0200
    Bug#1114894: OS-Prober generates not running entries for Debian 12 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2025-09-17 00:30 +0200
      Bug#1114894: OS-Prober generates not running entries for Debian 12 Debian <debian@decotrain.de> - 2025-09-17 09:50 +0200

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

Package: grub2-common
Version: 2.12-9
Severity: important


Hello,

the OS-Prober does generate not running entries for Debian 12.
(Debian 8, 11 and 13 is working on other partitions.)

Instead of

     linux /boot/vmlinuz-6.1.0-39-amd64 
root=UUID=699e8929-8bdf-4b9f-9191-cf922ef52df3 ro quiet
     initrd /boot/initrd.img-6.1.0-39-amd64

this entry is generated, that ends somehow in a shell without starting 
the graphical interface

         linux /vmlinuz root=/dev/sda2
         initrd /initrd.img

The grub.cfg has been edited manually now and then it works for all 
different OS-versions.

Best regards
karsten


-- Package-specific info:
*********************** BEGIN /proc/mounts
/dev/sdb5 / ext4 rw,noatime,discard,errors=remount-ro 0 0
/dev/sda6 /win ext4 rw,relatime 0 0
/dev/sda7 /srv ext4 rw,relatime 0 0
*********************** END /proc/mounts

*********************** BEGIN /boot/grub/grub.cfg
...
menuentry 'Debian GNU/Linux 13 (trixie) on SSD' --class debian --class 
gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-simple-d3638439-6781-49a7-a8d7-4aa8d8b92b3a' {
     load_video
     insmod gzio
     if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
     insmod part_msdos
     insmod ext2
     set root='hd0,msdos5'
     if [ x$feature_platform_search_hint = xy ]; then
       search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 
d3638439-6781-49a7-a8d7-4aa8d8b92b3a
     else
       search --no-floppy --fs-uuid --set=root 
d3638439-6781-49a7-a8d7-4aa8d8b92b3a
     fi
     echo    'Loading Linux 6.12.43+deb13-amd64 ...'
     linux    /boot/vmlinuz-6.12.43+deb13-amd64 
root=UUID=d3638439-6781-49a7-a8d7-4aa8d8b92b3a ro  quiet
     echo    'Loading initial ramdisk ...'
     initrd    /boot/initrd.img-6.12.43+deb13-amd64
}

...

menuentry 'Debian GNU/Linux 12 (bookworm) (on /dev/sdb2)' --class debian 
--class gnu-linux --class gnu --class os $menuentry_id_option 
'osprober-gnulinux-simple-699e8929-8bdf-4b9f-9191-cf922fe52df3' {
     insmod part_msdos
     insmod ext2
     set root='hd1,msdos2'
     if [ x$feature_platform_search_hint = xy ]; then
       search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 
--hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 
699e8929-8bdf-4b9f-9191-cf922fe52df3
     else
       search --no-floppy --fs-uuid --set=root 
699e8929-8bdf-4b9f-9191-cf922fe52df3
     fi
     linux /boot/vmlinuz-6.1.0-39-amd64 root=/dev/sdb2
     initrd /boot/initrd.img-6.1.0-39-amd64
}
submenu 'Advanced options for Debian GNU/Linux 12 (bookworm) (on 
/dev/sdb2)' $menuentry_id_option 
'osprober-gnulinux-advanced-699e8929-8bdf-4b9f-9191-cf922fe52df3' {
     menuentry 'Debian GNU/Linux 12 (bookworm) (on /dev/sdb2)' --class 
gnu-linux --class gnu --class os $menuentry_id_option 
'osprober-gnulinux-/boot/vmlinuz-6.1.0-39-amd64--699e8929-8bdf-4b9f-9191-cf922ef52df3' 
{
         insmod part_msdos
         insmod ext2
         set root='hd1,msdos2'
         if [ x$feature_platform_search_hint = xy ]; then
           search --no-floppy --fs-uuid --set=root 
--hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 
--hint-baremetal=ahci1,msdos2  699e8929-8bdf-4b9f-9191-cf922ef52df3
         else
           search --no-floppy --fs-uuid --set=root 
699e8929-8bdf-4b9f-9191-cf922ef52df3
         fi
         linux /boot/vmlinuz-6.1.0-39-amd64 root=/dev/sdb2
         initrd /boot/initrd.img-6.1.0-39-amd64
     }
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
if [ "$grub_platform" = "efi" ]; then
     fwsetup --is-supported
     if [ "$?" = 0 ]; then
         menuentry 'UEFI Firmware Settings' $menuentry_id_option 
'uefi-firmware' {
             fwsetup
         }
     fi
fi
### 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 ###
*********************** END /boot/grub/grub.cfg

*********************** BEGIN /proc/mdstat
cat: /proc/mdstat: No such file or directory
*********************** END /proc/mdstat

*********************** BEGIN /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root  9 Sep 11 11:24 ata -> ../../sdb
lrwxrwxrwx 1 root root 10 Sep 11 11:24 ata-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Sep 11 11:24 ata-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Sep 11 11:24 ata-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Sep 11 11:24 ata-part4 -> ../../sdb4
lrwxrwxrwx 1 root root 10 Sep 11 11:24 ata-part5 -> ../../sdb5
lrwxrwxrwx 1 root root 10 Sep 11 11:24 ata-part6 -> ../../sdb6
...
*********************** END /dev/disk/by-id

-- System Information:
Debian Release: 13.1
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.43+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE 
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages grub2-common depends on:
ii  dpkg                1.22.21
ii  grub-common         2.12-9
ii  libc6               2.41-12
ii  libdevmapper1.02.1  2:1.02.205-2
ii  libefiboot1t64      38-3.1+b1
ii  libefivar1t64       38-3.1+b1
ii  liblzma5            5.8.1-1

grub2-common recommends no packages.

grub2-common suggests no packages.

-- no debconf information

[toc] | [next] | [standalone]

#1260958

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 ?

>          linux /vmlinuz root=/dev/sda2
>          initrd /initrd.img

Is it the exact generated entry ?
What is the output of linux-boot-prober /dev/sda2 (or whatever the 
correct partition is) ?

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 grub.cfg has been edited manually now and then it works for all 
> different OS-versions.

Is this the edited menu entry ?

>      linux /boot/vmlinuz-6.1.0-39-amd64 root=/dev/sdb2
>      initrd /boot/initrd.img-6.1.0-39-amd64

[toc] | [prev] | [next] | [standalone]

#1261081

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
>

[toc] | [prev] | [next] | [standalone]

#1261177

On 12/09/2025 at 11:04, Debian wrote:
> Am 11.09.25 um 13:38 schrieb Pascal Hambourg:
>>
>>>          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.

Above ? I do not see any such entry in grub.cfg in your initial report.
Can you attach the full contents of /boot/grub/grub.cfg in Debian 12 
root filesytem ?

> The error occurs after the upgrade when grub has been installed in 
> Debian 13.

Which upgrade ?

[toc] | [prev] | [next] | [standalone]

#1261190

Am 13.09.25 um 10:55 schrieb Pascal Hambourg:
> Above ? I do not see any such entry in grub.cfg in your initial report.

Copied from the initial report:

*********************** BEGIN /boot/grub/grub.cfg
...
menuentry 'Debian GNU/Linux 13 (trixie) on SSD' --class debian --class
gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-simple-d3638439-6781-49a7-a8d7-4aa8d8b92b3a' {
     load_video
     insmod gzio
     if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
     insmod part_msdos
     insmod ext2
     set root='hd0,msdos5'
     if [ x$feature_platform_search_hint = xy ]; then
       search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5
d3638439-6781-49a7-a8d7-4aa8d8b92b3a
     else
       search --no-floppy --fs-uuid --set=root
d3638439-6781-49a7-a8d7-4aa8d8b92b3a
     fi
     echo    'Loading Linux 6.12.43+deb13-amd64 ...'
     linux    /boot/vmlinuz-6.12.43+deb13-amd64
root=UUID=d3638439-6781-49a7-a8d7-4aa8d8b92b3a ro  quiet
     echo    'Loading initial ramdisk ...'
     initrd    /boot/initrd.img-6.12.43+deb13-amd64
}

...

menuentry 'Debian GNU/Linux 12 (bookworm) (on /dev/sdb2)' --class debian
--class gnu-linux --class gnu --class os $menuentry_id_option
'osprober-gnulinux-simple-699e8929-8bdf-4b9f-9191-cf922fe52df3' {
     insmod part_msdos
     insmod ext2
     set root='hd1,msdos2'
     if [ x$feature_platform_search_hint = xy ]; then
       search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2
--hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2
699e8929-8bdf-4b9f-9191-cf922fe52df3
     else
       search --no-floppy --fs-uuid --set=root
699e8929-8bdf-4b9f-9191-cf922fe52df3
     fi
     linux /boot/vmlinuz-6.1.0-39-amd64 root=/dev/sdb2
     initrd /boot/initrd.img-6.1.0-39-amd64
}
submenu 'Advanced options for Debian GNU/Linux 12 (bookworm) (on
/dev/sdb2)' $menuentry_id_option
'osprober-gnulinux-advanced-699e8929-8bdf-4b9f-9191-cf922fe52df3' {
     menuentry 'Debian GNU/Linux 12 (bookworm) (on /dev/sdb2)' --class
gnu-linux --class gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-6.1.0-39-amd64--699e8929-8bdf-4b9f-9191-cf922ef52df3'
{
         insmod part_msdos
         insmod ext2
         set root='hd1,msdos2'
         if [ x$feature_platform_search_hint = xy ]; then
           search --no-floppy --fs-uuid --set=root
--hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2
--hint-baremetal=ahci1,msdos2  699e8929-8bdf-4b9f-9191-cf922ef52df3
         else
           search --no-floppy --fs-uuid --set=root
699e8929-8bdf-4b9f-9191-cf922ef52df3
         fi
         linux /boot/vmlinuz-6.1.0-39-amd64 root=/dev/sdb2
         initrd /boot/initrd.img-6.1.0-39-amd64
     }
}
### END /etc/grub.d/30_os-prober ###



> 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.


>> The error occurs after the upgrade when grub has been installed in 
>> Debian 13.
>
> Which upgrade ?

It seems to be confusing for you. :-)

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

Debian 12 is installed in /dev/sdb2 and has been copied to /dev/sdb5.
It was not easy to boot the copy in /dev/sdb5, but after about 3 attempts it works and the copy has been upgraded to Debian 13, after the modify of sources.list

In the upgrade process grub has been installed in /dev/sdb5, so it is not booted any more from /dev/sdb2.

[toc] | [prev] | [next] | [standalone]

#1261211

On 13/09/2025 at 12:51, Debian wrote:
> Am 13.09.25 um 10:55 schrieb Pascal Hambourg:
>> I do not see any such entry in grub.cfg in your initial report.
> 
> Copied from the initial report:

Again, I do not see any line "linux /vmlinuz root=/dev/sda2" here.

>> 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.

>>> The error occurs after the upgrade when grub has been installed in 
>>> Debian 13.
>>
>> Which upgrade ?
> 
> It seems to be confusing for you. :-)
(...)
> Debian 12 is installed in /dev/sdb2 and has been copied to /dev/sdb5.

How was I supposed to know about that ?

> It was not easy to boot the copy in /dev/sdb5

If 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.

[toc] | [prev] | [next] | [standalone]

#1261325

[Multipart message — attachments visible in raw view] — view raw

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/sdb5
>
> If 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.

[toc] | [prev] | [next] | [standalone]

#1261431

On 14/09/2025 at 09:28, Debian wrote:
> 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

They do not match "linux /vmlinuz root=/dev/sda2" in any way: the kernel 
and initramfs pathnames and the root device are different.

>>>> Can you attach the full contents of /boot/grub/grub.cfg in Debian 12 
>>>> root filesytem ? 
>> 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.

Ideally, linux-boot-prober collects menu entry information (entry label, 
kernel path and parameters...) from grub.cfg when it is present.
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) ?

[toc] | [prev] | [next] | [standalone]

#1261794

On 16/09/2025 at 22:14, Debian wrote:
> 
> A new update-grub is called in Debian 13 and the syslog output is attached.
> Hopefully this will help.

It looks like /dev/sdb2 has the wrong /boot/grub/grub.cfg which has menu 
entries for /dev/sdb1 ('Debian GNU/Linux 11 SSD', 'Linux 
5.10.0-35-amd64'). This is why linux-boot-prober cannot match the menu 
entries in this file with the 6.1.0-39 kernel image in the partition. It 
also looks like /vmlinuz and /initrg.img are real files instead of the 
usual symlinks pointing to the files in /boot.

Try to boot into bookworm on /dev/sdb2, run update-grub, then reboot on 
trixie and run update-grub.

[toc] | [prev] | [next] | [standalone]

#1261816

Am 17.09.25 um 00:18 schrieb Pascal Hambourg:
>
> It looks like /dev/sdb2 has the wrong /boot/grub/grub.cfg which has 
> menu entries for /dev/sdb1 ('Debian GNU/Linux 11 SSD', 'Linux 
> 5.10.0-35-amd64').

Why the OS-prober is searching in grub.cfg to find out how to address 
the partition?
The name or UUID of the partition of the OS is clear when accessing it.

That's the bad solution to get the right information.
When this works for most of the installations it's fine, but it is not a 
good solution.

> This is why linux-boot-prober cannot match the menu entries in this 
> file with the 6.1.0-39 kernel image in the partition. It also looks 
> like /vmlinuz and /initrg.img are real files instead of the usual 
> symlinks pointing to the files in /boot.

That's what you find in / on /dev/sdb2

lrwxrwxrwx   1 root root   27  7. Sep 17:32 vmlinuz-> 
boot/vmlinuz-6.1.0-39-amd64
lrwxrwxrwx   1 root root   27  7. Sep 17:36 vmlinuz.old-> 
boot/vmlinuz-6.1.0-39-amd64

> Try to boot into bookworm on /dev/sdb2, run update-grub, then reboot 
> on trixie and run update-grub.

Before everything was booted with the grub from /dev/sdb2 and it did work.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web