Bug 88194 - Boot Disk Verication Error
Boot Disk Verication Error
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Boot Disk Creation
Depends On:
  Show dependency treegraph
Reported: 2003-04-07 11:55 EDT by martin
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-18 16:46:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description martin 2003-04-07 11:55:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312

Description of problem:
During the Red Hat 9.0 installation, when making a boot disk get verication
error.  Same disk works fine under Red Hat 8.0 Boot Disk Creation.  Does not
allow you to create a known good Boot Disk.

Version-Release number of selected component (if applicable):
Red Hat 9.0 Installation

How reproducible:

Steps to Reproduce:
1. Click on make Boot disk during Red Hat 9.0 Installation
2. Writes to Floppy Disk 
3. Error comes up with unable to verify disk
4. Ask to create another boot disk
5. Click on make another boot disk and get same error every time.  

Actual Results:  Verification boot disk error

Expected Results:  Disk should have verified that it was good and continued

Additional info:

I had no problems with the 8.0 boot disk creation during install but get this
error everytime during 9.0 installation.  I feel that there is a bug in the
newly 9.0 release.
Comment 1 Jeremy Katz 2003-04-07 14:27:50 EDT
What is the text of the error message you receive?
Comment 2 Michael Fulbright 2003-06-18 16:46:18 EDT
Closing due to inactivity - please reopen if you have additional information to add.

Note You need to log in before you can comment on or make changes to this bug.