I believe that the delay and the fd0 read error are two separate issues
occurring together.
I have the same issue with the fd0 read error, however on this machine
it doesn't cause any additional delay, in fact I had to reboot four
times to get all parts of the message. I have other machines that do
have a delay in loading the grub menu, usually due to loading an image
or lvm scans with more than a couple volumes. I've always chalked up the
grub delay to the multiple "search ... --set=root ..." commands causing
multiple full scans, but am not entirely sure. What is your drive
configuration?
As for the fd0 error, I've seen some reports that disabling the floppy
controller in the BIOS will eliminate that, presumably grub scanning all
devices about which it knows or can detect. On this laptop, however,
there isn't a way to disable the floppy controller entirely, just
disable the boot order entry. It would be nice to tell grub to ignore
the fd0 device even if it is detected. The device.map file used to do
that, but my /boot/grub/device.map file only has a single (hd0) entry
for the /dev/disks/by-id/X entry.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
