[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/568720
the fd0 message disappers after disabling the floppy drive but the
ubuntu does not start at all. the pink screen appears for 10 minutesa nd
it goes black again..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Loic, are you quite sure you disabled the floppy in the bios, and did
you ever collect the debug output?
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same thing on Precise with Grub2 1.99-21ubuntu3.4. This appears to be
due to Grub2 searching an lvm partition for unicode.pf2. Here's a
workaround for those using a separate, non-lvm /boot partition. Note: I
am not sure if this will work with other distributions or Grub2
versions.
1) sudo cp
I can add a bit of seriousness here:
On booting I'm getting
errors: fd0: read error
errors: fd1: read error
If I remove my USB 2.0 Card Reader 35 in 1 the read errors on booting
disappear. There is only one bootable device in the bios, an SSD drive,
on sda. When I set up the system this morning
Have the same issue here. In my case though, it's not a floppy drive,
it's my USB multi-card reader, which doesn't have any cards in it
actually. I guess my BIOS is emulating those card slots as floppy
drives, yet I don't see a way to disable it. I would really like to
force GRUB or LVM to ignore
Bought a Zotac Zbox for home internal gateway. Initial install no
problems. When attempting to re-install, Zbox will not boot off USB -
get the 'error fd0 read error'. Turned off USB legacy support and it
ignores USB all together. Order a USB DVD drive as a work around. I have
noticed the error on
I had this problem on Ubuntu 11.10 64-bit with grub-pc 1.99-12ubuntu5.
The PC has a Gigabyte board with Award BIOS v 6.00PG.
The workaround suggested above worked -- I disabled FDD in BIOS:
Standard CMOS Features - Drive A: None
--
You received this bug notification because you are a member of
** Changed in: grub2 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/568720
Title:
Error scanning for fd0 on boot
To manage notifications about this bug go
Same problem on Lucid server but I think I caused it
The boot was clean until I installed 2tb drives and messed up (I think).
I recently set up a Dell Precision 390 (no floppy) with two WD 80Gb
disks with three partitions (swap root and userspace) in raid 1 under MD
Everything was fine until
Today I did a clean install from the Kubuntu 11.04 DVD on a brand new
PC. Custom RAID partitioning of two SATA HDDs, and at startup after BIOS
I get a long pause (30s or more) followed by the same error, “error: fd0
read error.” on the screen for many seconds, probably a minute or more,
before the
The message seems to be generated in /boot/grub/biosdisk.mod from this
format string:
%s read error
And it *is* probing an empty floppy drive. I only get this error since I
enabled the floppy controller to be able to read some ancient software
from floppies. I forgot to test with a medium in the
@Lupe Christoph:
See the link I posted:
http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg767224.html
Vladimir Serbinenko, apparently a grub developer, says there:
Actually the problem in this bug reports is lvm and mdraid. The problem
is that some BIOSes expose USB HDD as
Apparently, this affects Debian as well and has been recognized about
half a year ago, but I can't seem to find out if it's been fixed.
http://www.mail-archive.com/debian-bugs-
d...@lists.debian.org/msg767224.html
--
Error scanning for fd0 on boot
https://bugs.launchpad.net/bugs/568720
You
- grep'ing /etc/grub.d/ for fd0 yields no results, so the problem probably
doesn't lie there.
- disabling my FDD is not an option for me, because I want to _use_ it (just
not at boot)
--
Error scanning for fd0 on boot
https://bugs.launchpad.net/bugs/568720
You received this bug notification
** Changed in: grub2 (Ubuntu)
Assignee: Colin Watson (cjwatson) = (unassigned)
--
Error scanning for fd0 on boot
https://bugs.launchpad.net/bugs/568720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm suffering it too. I also suffer the 5-10 seconds delay when the message
appears.
- When I disable BIOS option (Legacy FDD), the message dissapears (but due to a
bios bug, the system refuses to start sometimes when I disable the option!)
- I've tried grub-install --no-floppy several times,
Steps to debug this:
* edit /usr/sbin/grub-install to land some code in load.cfg
* the code should be set debug=disk or set debug=all
* also add option to padd -c load.cfg in the case where it's an abstracted
device
This should turn on debug in grub2 and should explain why floppy is
probed.
--
Might also be the BIOS booting the (failed) drive carrying and old mbr.
--
Error scanning for fd0 on boot
https://bugs.launchpad.net/bugs/568720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Simply disabling the floppy in the BIOS fixed it for me.
--
Error scanning for fd0 on boot
https://bugs.launchpad.net/bugs/568720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I also observed the message error: fd0 read error. on my intel core
duo laptop. I was also able to make it go away by disabling legacy FDD
emulation in the BIOS. (In my Toshiba QOSMIO BIOS, the entry is USB-
FDD Legacy Emulation. No floppy is connected.)
I confirmed that the message was being
On Wed, 2010-04-28 at 20:56 +, Sean Sheedy wrote:
The presence of the message does not appear to delay or interfere with
the presentation of the grub2 menu, which appears shortly afterward, and
from which booting proceeds normally.
It was delaying it here about 5-10 seconds. Just
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/45050753/Dependencies.txt
--
Error scanning for fd0 on boot
https://bugs.launchpad.net/bugs/568720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
23 matches
Mail list logo
