Bug 1115026

Summary: grub2 30_os-prober hangs if no legacy floppy drive present in the system
Product: [Fedora] Fedora Reporter: Pasi Karkkainen <pasik>
Component: os-proberAssignee: Hedayat Vatankhah <hedayatv>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bcl, hedayatv, lkundrak, mads, pasik, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-08 18:01:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda log from the problematic system where os-prober hangs none

Description Pasi Karkkainen 2014-07-01 12:49:40 UTC 
Description of problem:

I tried installing Fedora 20 on an old HP Proliant DL380 G4 server. This server does not have a legacy floppy drive installed/present. (But I believe there is an emulated USB remote media floppy drive in the iLO management processor).

Installation went OK until anaconda started installing bootloader, which got stuck. I waited for around 30 minutes and it was still stuck..

I switched to the console and noticed lots of IO errors about fd0 in kernel dmesg. I also checked the process list, and I noticed grub 30_os-prober is running (well, stuck).

Killing os-prober process made anaconda continue (to generate a crash report).

Version-Release number of selected component (if applicable):
Fedora 20 DVD installer.

How reproducible:
Always.

Steps to Reproduce:
1. Try installing Fedora 20 on a system without legacy floppy drive.
2. os-prober gets stuck, preventing bootloader from being installed and fedora installation successfully finishing.


Actual results:
30_os-prober gets stuck.


Expected results:
30_os-prober does not get stuck or hang, bootloader is successfully installed.



Additional info:

While 30_os-prober is being executed (and is stuck) I'm seeing a lot of these errors in dmesg:

[  593.477948] end_request: I/O error, dev fd0, sector 0
[  593.477957] Buffer I/O error on device fd0, logical block 0
[  606.553982] end_request: I/O error, dev fd0, sector 0
[  606.553991] Buffer I/O error on device fd0, logical block 0
[  619.629789] end_request: I/O error, dev fd0, sector 0
[  619.629798] Buffer I/O error on device fd0, logical block 0
Comment 1 Brian Lane 2014-07-01 15:34:35 UTC 
Please attach the anaconda logs from /tmp/*log to this bug as individual text/plain attachments.
Comment 2 Pasi Karkkainen 2014-07-03 19:59:54 UTC 
Created attachment 914583 [details]
anaconda log from the problematic system where os-prober hangs
Comment 3 Pasi Karkkainen 2014-07-03 20:02:01 UTC 
I hope that the attached anaconda.log from the installed system is OK.. 

Note that I manually killed the 30_os-prober process so that's why you see the exception/traceback "BootLoaderError: failed to write bootloader configuration".
Comment 4 Brian Lane 2014-07-08 17:20:30 UTC 
I'm not sure if there is anything os-prober can do, it looks like the kernel thinks there is media in the drive so you're getting I/O errors. Best thing would be to disconnect the virtual floppy if possible.

Passing this to os-prober for comment.
Comment 5 Pasi Karkkainen 2014-07-08 17:27:07 UTC 
There wasn't any media mounted to the virtual/remote floppy.. (only DVD ISO mounted to the remote CD/DVD drive, for Fedora installation).

When entering the Fedora rescue mode, and chrooting into /mnt/sysimage, I had to "chmod a-x 30_os-prober" first before I was able to manually fix grub. Otherwise grub would just hang/stall, just like during Fedora installation.
Comment 6 Hedayat Vatankhah 2014-07-08 18:01:39 UTC 
If your problem is like problem seen in other systems, you should be able to avoid this problem by disabling the floppy drive controller in your BIOS/UEFI configuration. In my experience, I've got I/O errors on systems in which floppy drive controller is enabled. 
However, in all previous experiences of this problem, os-prober FINALLY passes this step (I don't know how much time I've wait for this to happen, but it took long). 

What I'm thinking about is to completely disable scanning /dev/fdX in os-prober. It might not be a "proper" solution but possibly it is a minor issue (I wonder how many people might want to have a menu entry for an OS on a floppy disk!).

*** This bug has been marked as a duplicate of bug 972670 ***