Bug 61760 - installation fail
installation fail
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-03-24 03:44 EST by Need Real Name
Modified: 2008-05-01 11:38 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:48:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
installation bug log file (77.34 KB, patch)
2002-03-24 03:50 EST, Need Real Name
no flags Details | Diff
Comment (77.98 KB, text/plain)
2002-03-24 03:44 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2002-03-24 03:44:46 EST
Created attachment 915096 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).
Comment 1 Need Real Name 2002-03-24 03:50:37 EST
Created attachment 49928 [details]
installation bug log file
Comment 2 Allan A. B. Thomsen 2002-03-24 10:25:45 EST
Hi,

I have a device timeout error on a SCSI device, look similar let me know if you wan't the dump file.

Regards,

Allan A. B. Thomsen
allan@proport.dk
Comment 3 Jeremy Katz 2002-03-25 14:45:03 EST
Are these on CDs you burned yourself?
Comment 4 Allan A. B. Thomsen 2002-03-26 09:03:38 EST
Yes, from images downloaded from redhat.com. I am trying to test an upgrade 
from the "licensed" version 7.1 that I have.
Comment 5 Jeremy Katz 2002-03-26 15:16:30 EST
Do the md5sums of the images match the ones published on our FTP site?   There
are a number of I/O errors in your syslog which usually implies bad CDs.
Comment 6 Michael Fulbright 2002-04-15 18:26:07 EDT
Closing due to inactivity please reopen if you have additional problems.
Comment 7 Red Hat Bugzilla 2006-02-21 13:48:37 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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