os-prober doesn't detect EFI boot partitions on mdraid devices in dual boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-prober (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu Version:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Package Version:
os-prober:
Installed: 1.74ubuntu2
Candidate: 1.74ubuntu2
Version table:
*** 1.74ubuntu2 500
500 http://
100 /var/lib/
Given the following setup:
Given a configuration with boot partition on non bios raid drive, and Another OS with its own boot partition (such as Windows) on bios raid drive. User is desiring to chainload the other os from grub.
What should happen:
OS Prober detects Other OS's boot partition (such as windows) and forward the correct EFI file to grub during configuration. Grub now knows about the other OS and will show up in menu to be chainloaded.
What happens:
os-prober skips the mounted boot partition on the bios raid device because it gets caught by the "Is this a virtual device" check on line 32 of /usr/lib/
Summary:
Due to the restrictive conditional in /usr/lib/
tags: | added: rls-ff-incoming |
tags: |
added: rls-ff-notfixing removed: rls-ff-incoming |
The attachment "potential fix for allowing os-prober to detect other os's on bios raid drives loaded by mdadm." seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]