Red Hat Bugzilla – Bug 490739
anaconda probes for non-existing fd0 for 10 minutes
Last modified: 2009-04-29 15:30:38 EDT
This looks like it could be a pyparted bug, but the log message that makes me think this ("creating parted Disk /dev/fd0") could also be a red herring. Please test tomorrow's build of anaconda which will move this log message to the right place and attach a new storage.log so we can see what's really going on. Thanks.
Have you been able to try the latest nightly rawhide tree to see if this problem is still present?
Created attachment 336458 [details]
/tmp/storage.log from anaconda 220.127.116.11
problem persists with anaconda 18.104.22.168, seet attached storage.log
storage.log was retrieved from the node after waiting for the timeout on fd0 and then clicking 'ignore drive'.
As of today this problem still exists. Running from preupgrade if that helps.
problem still exists in anaconda 22.214.171.124
Interesting. I tried to do an upgrade using the netboot method instead of preupgrade, which is broken because of another bug.
When I go into the secondary ctrl alt screens I find that it is apparently trying to format the floppy drive. With each track erroring out. If you had a disk in the drive that was just not fedora compatible that could really be a bad issue.
problem still exists with anaconda 126.96.36.199
This problem also occurs when trying to get into rescue mode.
This is the same as/ related to
I can confirm that this bug is fixed in anaconda 188.8.131.52
This bug can be CLOSED RAWHIDE
How does one access these new versions of anaconda for testing?
Actually I should probably make my question more specific. I understand the update.img thing and how to use it, but where would find the right update.img thing to use the right anaconda.
Closing per comment #12.
this bug is back in F11 Preview (anaconda 184.108.40.206) but at least after the 10 minute wait I can now click ignore after 10ish minutes and continue install.
For F11 I'm kinda sorta OK as I only see this on one hardware variant, but this needs to be resolved by RHEL 6 or the customer I am sitting at will be VeryUnhappy(tm)
What can I do to make this bug once again go away?
aaah, Haisenbugs, don't we love them
same anaconda version but with latest rawhide from my mirror, error is gone again.
Not quite sure what to do now.
nevermind, I am an idiot.
Comment #16 and #18 were done with the kernel & initrd of F11 Preview but the ks file pointed at F11 Beta (my punishment for copying old ks files and then editing them or as in this case forgetting to edit them).
Sorry about the noise. All is well WRT this bug in F11 Preview.