Red Hat Bugzilla – Bug 62929
Bad floppy is accepted for floppy bootdisk creation
Last modified: 2007-03-26 23:52:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Description of problem:
A corrupted floppy was used for the boot floppy creation phase of installation.
The system indicated the boot disk was successfully created. Floppy failed at
boot time when it went to the VMLINUZ load. Checked floppy and found that it
could not be formatted at all.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Get a corrupt (non-formattable) floppy
2. Use it in the boot floppy phase of the install
3. Reboot using it
Expected Results: If the floppy was bad then Anaconda should have detected it.
A quick verify after writing the data should be utilized. Give the user a
chance to redo this phase using a fresh floppy if an error is detected.
This is a problem that occurs often with rawrite or dd of images onto damaged
floppies. The only way to protect yourself from this is to format a floppy
beforehand and be sure there are no bad sectors.
Would it be possible for Anaconda to do this format check before writing the
I will make this a request for a future release, we cannot make these types of
We now check to ensure that the initrd and kernel we wrote to the boot floppy
are the size we expected them to be.