Description of problem: An error is occurred when probing FAT32 windows partition, that it cannot be unmounted due to being busy. Version-Release number of selected component (if applicable): grub2-tools-2.0-0.39.fc17.x86_64 How reproducible: Run grub2-mkconfig Steps to Reproduce: 1. Execute: grub2-mkconfig -o /boot/grub2/grub.cfg 2. 3. Actual results: Generating grub.cfg ... Found theme: /boot/grub2/themes/system/theme.txt Found linux image: /boot/vmlinuz-3.6.11-1.fc17.x86_64 Found initrd image: /boot/initramfs-3.6.11-1.fc17.x86_64.img Found linux image: /boot/vmlinuz-3.6.10-2.fc17.x86_64 Found initrd image: /boot/initramfs-3.6.10-2.fc17.x86_64.img Found linux image: /boot/vmlinuz-3.6.9-2.fc17.x86_64 Found initrd image: /boot/initramfs-3.6.9-2.fc17.x86_64.img No volume groups found umount: /var/lib/os-prober/mount: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy Found Microsoft Windows 2000 Professional on /dev/sdb1 Found Fedora release 10 (Cambridge) on /dev/sdb2 done Expected results: No umount errors should have occurred. Additional info: The partition is remained mounted after the command has finished: /dev/sdb9 2901117 2334193 566924 81% /var/lib/os-prober/mount and it is of type: /dev/sdb9 154224063 160071659 2923798+ b W95 FAT32
The mentioned system has been upgraded to Fedora 18 and the problem still occurs. The relative for F18 is Bug 903906 as cloned by Matthew Hassel.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.
The issue stills happens in Fedora 19: # grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub.cfg ... Found theme: /boot/grub2/themes/system/theme.txt Found linux image: /boot/vmlinuz-3.10.4-300.fc19.x86_64 Found initrd image: /boot/initramfs-3.10.4-300.fc19.x86_64.img Found linux image: /boot/vmlinuz-3.10.3-300.fc19.x86_64 Found initrd image: /boot/initramfs-3.10.3-300.fc19.x86_64.img Found linux image: /boot/vmlinuz-0-rescue-46379777f22e4264267f50bf4a3f6eb6 Found initrd image: /boot/initramfs-0-rescue-46379777f22e4264267f50bf4a3f6eb6.img umount: /var/lib/os-prober/mount: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) rmdir: failed to remove ‘/var/lib/os-prober/mount’: Device or resource busy Found Microsoft Windows 2000 Professional on /dev/sdb1 Found Fedora release 10 (Cambridge) on /dev/sdb2 done
Is it possible to umount /var/lib/os-prober/mount after running os-prober manually?
Yes, it is, but this is a workaround and not a solution.
Yes, I'm not talking about a solution, I'm talking about the problem! Do you use KDE? or any KDE software before running os-prober? Do you always see this problem or sometimes?
I think I have proved with strace in Bug 903906 that KDE and more specific plasma-desktop is the one to blame. Running the grub2-mkconfig command from a alt-ctrl-F2 console, without being logged to KDE the issue is not observed. From within KDE session, it is always reproduced.
I don't usually compare the reporter of different bugs. You could tell me earlier (or mark as duplicate yourself) *** This bug has been marked as a duplicate of bug 903906 ***