Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 85734

Summary: Boot disk fails
Product: [Retired] Red Hat Public Beta Reporter: Jeff Collins <jeffrey_collins>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: high Docs Contact:
Priority: medium    
Version: phoebe   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-03-07 16:04:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jeff Collins 2003-03-06 18:02:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; H010818; .NET 
CLR 1.0.3705)

Description of problem:
I'm trying to install Redhat Beta (Phoebe-re0214.Beta5-RC6-i386).  I created a 
boot disk and after selecting either graphical mode or text mode to install 
with, the boot disk fails.  It happens while it's loading initrd.img.  It fails 
with this message, "Boot failed: please change disks and press a key to 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a boot disk from bootdisk.img using dd if=bootdisk.img of=/dev/fd0
2. Boot the system with the boot disk
3. Select either graphical or text install method


Actual Results:  While loading initrd.img, the install fails with this 
message, "Boot failed: please change disks and press a key to continue."

Expected Results:  Setup for Redhat Beta continues

Additional info:
This bug probably shouldn't be assigned to setup, but I'm not sure where to 
assign it to.  The list of places to assign bugs is too long and vague.

Comment 1 Jeremy Katz 2003-03-07 16:04:44 UTC
You have a bad floppy disk.  Try again with another floppy and you shouldn't
have a problem.