Bug 122033

Summary: CD install will not proceed if a CD read error occurs
Product: [Fedora] Fedora Reporter: Thorn Roby <troby>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: don
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-06 22:09:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Thorn Roby 2004-04-29 20:33:55 UTC 
Description of problem:
Disk 2 produced a read error on zlib-devel, continually prompted to
retry, would not release CD drive without forcing open with a paper
clip. When this was done and the disk re-inserted, the read was
successful and installation continued. The disk had been tested before
installation and successfully used on a previous installation.

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

FC2T3
How reproducible:

One time only
Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:

There should be a way to abort the read of a particular component, or
at least the ability to open the drive and re-insert the disk.

Additional info:
Comment 1 Jeremy Katz 2004-05-06 22:09:14 UTC 
This should be fixed in CVS
Comment 2 don 2004-10-17 22:22:21 UTC 
Fedora Core 3 test 3: 

Well it eventually gives up, but there is still no "fail" or "eject
cd" options.

During installation if the installer is unable to read a package from
the CD, it times out, gives a message, and the only option is OK. You
have to do this three times until it gives up.
(With prereleases it's hard to tell whether the image test fails
because nobody bothered to get the checksum right, or if the CD really
does need to be re-burned)

First, shouldn't there be a choice to "Fail"?

Second, assuming the system will still work when it's booted, it might
be a good idea to say something like check the install log and be sure
to install this yourself.