os-prober failed
by Phiebie from LinuxQuestions.org on (#596T9)
Debian bullseye x86-64 up to date, Grub2 operational.
List of concerned partitions:
Quote:
sda1 has Windows 10
sda5 has Debian bullseye
sdc2 has Debian buster
sde1 has Debian buster
ALL 4 systems start flawlessly out of the BIOS-boot.
Running on sda5 the update-grub yields a grub.cfg with only sda1 and sda5 as choices.
Running on sda5 the pure os-prober yields as screen-output only sda1.
So in both cases /dev/sdc and /dev/sde are not considered.
When I however - a PITA - manually add both drives to the created grub.cfg, I then can also start the other systems from the grub-screen.
So there is nothing wrong with all boot-settings of the other 2 drives, only os-prober is blind.
Where could I look to cure this blindness?
Oh yes, I have reinstalled grub and os-prober already a couple of times and rebooted afterwards.
Regards.
List of concerned partitions:
Quote:
| Disk /dev/sda: 256.17 GiB, 275064201216 bytes, 537234768 sectors Disklabel type: dos Disk identifier: 0x1d166e73 Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 1026047 1024000 500M 7 HPFS/NTFS/exFAT /dev/sda2 1026048 203737346 202711299 96.7G 7 HPFS/NTFS/exFAT /dev/sda3 203739136 204799999 1060864 518M 27 Hidden NTFS WinRE /dev/sda4 204802048 532582399 327780352 156.3G 5 Extended /dev/sda5 204804096 217092095 12288000 5.9G 83 Linux ---------------------------------------------------------------------- Partition table scan /dev/sdc: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Number Start (sector) End (sector) Size Code Name 1 2048 4095 1024.0 KiB EF02 2 1130496 5861375 2.3 GiB 8304 ----------------------------------------------------------------------- Disk /dev/sde: 28.91 GiB, 31037849600 bytes, 60620800 sectors Disklabel type: dos Disk identifier: 0x79711288 Device Boot Start End Sectors Size Id Type /dev/sde1 * 2048 9764863 9762816 4.7G 83 Linux |
sda5 has Debian bullseye
sdc2 has Debian buster
sde1 has Debian buster
ALL 4 systems start flawlessly out of the BIOS-boot.
Running on sda5 the update-grub yields a grub.cfg with only sda1 and sda5 as choices.
Running on sda5 the pure os-prober yields as screen-output only sda1.
So in both cases /dev/sdc and /dev/sde are not considered.
When I however - a PITA - manually add both drives to the created grub.cfg, I then can also start the other systems from the grub-screen.
So there is nothing wrong with all boot-settings of the other 2 drives, only os-prober is blind.
Where could I look to cure this blindness?
Oh yes, I have reinstalled grub and os-prober already a couple of times and rebooted afterwards.
Regards.