Description of problem: I had a three disk Desktop. os-prober finds all operating systems (windows, 2xfedora18, and mint14 other. I received a virgin 1 terrabyte drive which I added to the system as sdd in the group sda, sdb, sdc, sdd. Hardware sees it as hd2. After installing the empty unformatted (factory fresh) disk and before installing a test tc3 version of Fedora 19 (rawhide), Fedora (os-prober) was only detecting Fedora18 (sda / hd0) and (sdc / hd3), containing a backup Fedora 18 installation. It was skipping windows and mint14. (hd3) After installing Fedora19 TC3 onto sdd the missing operating systems were caught and included to grub.cfg The missing disk allowed sdd/hd2 to be Version-Release number of selected component (if applicable): How reproducible: Add empty unformatted disk between hd0 and hd3. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: For some reason the 4th disk is known as hd2, and so, os-prober stopped scanning when it encountered the empty hd2. With F19 installed on hd2, F19 went on to include hd3, (all disks hd0..hd3) were scanned. instead of stopping after hd0,hd1.
Problem with F19 Alpha tc5. Same problem as with F18. Anaconda's grub or os_prober is not up to the same level as the one from standard libraries. Therefore, on reboot immediately following anaconda installation, we are missing operating systems in the newly created grub.cfg. Before applying patches to F19 (immediately following reboot), running grub2-mkconfig -o /boot/grub2/grub.cfg creates a good grub.cfg file
Are you talking about 1 problem or 2 problems: in the first case, does it detect all OSes if grub2-mkconfig is running after installation? (In both cases do you encounter the problem only during installation and not after installation?!)
No Osprober with F19 RC3 has been corrected
OK, thanks!