Description of problem: Installing on an old SuperMicro H8DCE 2-socket AMD 940 motherboard With ForcedEth ethernet, floppy controller enabled, but *NO* floppy powered. Late stage install of boot block fails with grub2-install step hanging attempting to access the floppy FD0, which in this case, does not exist. The retry does not time out even after 30 minutes. Version-Release number of selected component (if applicable): How reproducible: Install general workstation development on old AMD socket 940 motherboard. Leave the floppy drive unpowered. Steps to Reproduce: 1. 2. 3. Actual results: Hang in grub2- step trying for a floppy. <Alt><F4> shows grub2 step, and scrolling FD0 errors. Expected results: A grub2 boot block Additional info: Yeah, its old and in the way, but it didn't cost much :-) The forcedeth is not a valid ethernet device either (also no big deal).
I was able to reproduce the issue, and it was caused by blkid which is run inside os /bin/os-prober in function partitions. Changing component to util-linux. blkid was from: util-linux-2.23.2-14.el7
Any progress with this?
It would be nice to have /proc/partitions from the machine. libblkid should not read fd0 by default at all. It would be also nice to have output from LIBBLKID_DEBUG=0xffff blkid
Created attachment 876011 [details] blkid_debug
Created attachment 876012 [details] partitions
Hmm... it seems that we're affected by stupid kernel regression (which will not be fixed...), see https://groups.google.com/forum/#!topic/linux.kernel/uj-jvmwn9yg where kernel displays removable media in /proc/partitions now. It will be probably necessary to add an extra filter to libblkid to ignore by default the floppies.
The another story are mess in return codes in the library. It should be fixed together with the floppy problem.
Note that there is also kernel solution, see bug #1078786.
Fixed by upstream commits 296d96e20e565e497e9510e6ac9b71e0a0ca447d and 37f4060225df0591ab8e1dd676dbc8115d900d4f.
*** Bug 1081567 has been marked as a duplicate of this bug. ***
*** Bug 1082961 has been marked as a duplicate of this bug. ***
This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request.