Red Hat Bugzilla – Bug 51765
floppy access causes panic with bad media
Last modified: 2007-04-18 12:35:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT)
Description of problem:
During the bootnet install and later using 'mkbootdisk' manually, the
system hangs (motherboard/BIOS specific symptoms: power LED flashes, high
pitched beeeeeeep, floppy LED lit solid, no response to keyboard, etc).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mkbootdisk 2.4.2-2
(Reproduceable everytime inasmuch as this was only attempted twice - once
during the install, and once post-install.)
Actual Results: Reboot!
Grabbed a second floppy, and mkbootdisk worked flawlessly, so I don't
suspect the floppy drive itself.
Ran 'mkbadblocks' and 'chkdsk /r' (from NT4) to verify the first floppy
disk's integrity. No errors reported, but the latter might have silently
fixed the disk.
Re-ran mkbootdisk on the first floppy, and it worked. *sigh* It's now no
Suspect marginal quality media (albeit "name brand").
Expected Results: Should have recovered more gracefully, the first couple
CPU: Athlon TB 1 GHz
Mem: 1 Gb SDRAM
M/B: Asus A7A266
Sorry, I forgot to re-test this specifically from the shell with
mkbootdisk-1.4.8-1 before permanently discarding the bad media. However, the
RH8 GUI install did recover, detecting a problem while creating the boot disk on
the aforementioned bad media. If the GUI install uses mkbootdisk, then this bug
can be closed.