Description of problem: grub2-mkconfig and os-prober sometimes detect my two other Linux distributions (Mint 19 and Ubuntu 18) on the same disk, and some other times don't. It only detects Windows in another disk drive: root mortadelo ~ # root mortadelo ~ #os-prober /dev/sda4:Linux Mint 19.1 Tessa (19.1):LinuxMint:linux device-mapper: remove ioctl on osprober-linux-sda4 failed: Device or resource busy Command failed. /dev/sda6:Ubuntu 18.04.2 LTS (18.04):Ubuntu:linux device-mapper: remove ioctl on osprober-linux-sda6 failed: Device or resource busy Command failed. /dev/sdb2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi root mortadelo ~ # This issue causes the grub.cfg file on /boot/efi/EFI/fedora to be updated correctly with all the OSes sometimes, some other times no. This also happens when I install a new kernel. Version-Release number of selected component (if applicable): Fedora 30 How reproducible: Steps to Reproduce: 1. Run grub2-mkconfig -o /boot/efi/EFI/fedora/grub.conf. 2. When it works correctly, Mint and Ubuntu are detected and added to grub.cfg. 3. When it doesn't work, the following message appears and grub.cfg is not updated: /dev/sda4:Linux Mint 19.1 Tessa (19.1):LinuxMint:linux device-mapper: remove ioctl on osprober-linux-sda4 failed: Device or resource busy Command failed. /dev/sda6:Ubuntu 18.04.2 LTS (18.04):Ubuntu:linux device-mapper: remove ioctl on osprober-linux-sda6 failed: Device or resource busy Command failed. Actual results: grub.cfg doesn't contain entries for booting other Linux distributions. Expected results: grub.cfg should contain entries for booting Mint and Ubuntu (in my specific case). Additional info:
1. Yes, this is a known problem and can be fixed if os-prober is updated. However, it depends on bug #1471267 which is fixed in rawhide but not f30. I wonder if it'll be fixed for f30 too. And for most users, os-prober is only invoked once during installation; unless somebody runs grub2-mkconfig manually. It is never called automatically after installation. 2. It should NOT happen when you install a new kernel: grub2-mkconfig is not invoked when a new kernel is installed. New kernel entry will by added by grubby without probing for other OSes.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.