Red Hat Bugzilla – Bug 753643
error: fd0 read error. at boot + delay (grub2)
Last modified: 2013-02-17 00:53:43 EST
Description of problem:
Welcome to grub appear and then
error: fd0 read error.
is printed twice with several seconds delay
after a few more second, the classic grub menu appears
Version-Release number of selected component (if applicable):
fedora 16 + updates at 13nov (same with stock F16)
Steps to Reproduce:
1.switch on pc
2.after bios, grub start
delay and error messages above
go immediately to grub menu
using LVM + RAID1 + GPT
Tried to run :
grub2-install --no-floppy /dev/sda
grub2-install --no-floppy /dev/sdb
which return ok.
still same pb.
delay is nearly 40 seconds.
In my case I solved the problem by disabling small-USB-drives-as-FDD in my Xeon workstation's BIOS.
Did it work with previous grub versions?
I didn't have these issues w/ grub 1; it's grub2 specific.
Upstream grub2 maintainer sayz:
The problem only shows up on systems where the bios claims there are floppys around and raid or lvm is used for booting.
The solution is to convince the bios to stop lying to grub.
A workaround might be implemented later.
*** Bug 755173 has been marked as a duplicate of this bug. ***
I have the same problem on a fresh Fedora 16 installation (32 bit, so it's not 64 bit specific).
The BIOS correctly says that a floppy drive exist. There's no floppy disk in it, of course. I can clearly hear that GRUB2 checks the floppy drive during the boot process (two times), and then it prints two warnings. When it finds no disk, it should simply continue to boot from harddisk instead of forcing the user to hit a key or waiting for a time-out.
Is there a way to keep GRUB2 from accessing the floppy drive at all? (grub-install --no-floppy doesn't seem to have any effect)
Can you give f17 with the latest grub (2.00~beta2) a try?
The 2.00 use lazy scanning and floppies are read only when the raid / LV wasn't found on regulare HDD so this should be fixed. Can you confirm?
I have the same problem in F17. What info you need to solve it?
(In reply to comment #10)
> I have the same problem in F17. What info you need to solve it?
Please explain which symptoms you see (a screenshot / photo would be great) and what makes you sure that it is the same problem.
Please state which grub2 version you are using - and please make sure that you run something like
grub2-mkconfig -o /boot/grub2/grub.cfg
The requested information haven't been provided. Closing the assuming, assuming the problem has been solved in the current release.
I had the same problem with Grub2 after a fresh Fedora 18 installation with software RAID.
Grub2 checked the floppy-drive (which was not connected), gave an "Error reading sector xxx" and dumped my into a Grub2 rescue shell.
I also tried the --no-floppy, but that didn't have any effect.
Sadly, the BIOS did not give me an option to disable the floppy-drive.
-> I solved it by physically reconnecting a floppy-drive.
My motherboard is an ASUS P5K.