Bug 18379 - Installer and timed-out CDROM
Installer and timed-out CDROM
Status: CLOSED DUPLICATE of bug 15982
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-10-05 00:59 EDT by apeacock
Modified: 2007-04-18 12:28 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-10-05 12:27:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description apeacock 2000-10-05 00:59:26 EDT
This seems to be more of a Linux kernel problem than an installer problem,
nevertheless...

The installer is unable to correctly locate RPMs on  the CDROM after the
"installing image to hd" and "preparing to install" stages of the
installer, presumably because the drive spins down during that long amount
of inactivity, returning errors on terminal 4 after the installer finally
tries to access it again.

I have been able to get around the problem by switching to terminal 2
during the above mentioned stages and doing an 'ls' (or other access to the
disc) in the CDROM's directories every few minutes.

I also had this problem with 6.2.  I can replicate the error after
installing by mounting a CD, changing to one of its directories, waiting,
and then trying to tab-complete a filename.  The error reported is the same
as that reported on terminal 4.

The CDROM model is correctly identified by the BIOS and Linux as:
hdc: ZIPCD 4x650, ATAPI CDROM drive
Comment 1 Michael Fulbright 2000-10-05 12:27:51 EDT

*** This bug has been marked as a duplicate of 15982 ***
Comment 2 apeacock 2000-10-05 13:52:23 EDT
I'm not sure that this should be marked as duplicate of 15982.  Although the fix
may be related to the fix for that problem, the discs I used *are* valid images,
verified with MD5SUMs, and I was able to install using the method outlined above
(keeping the CD spinning in the drive instead of allowing it to spin down) from
them without flaw.

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