Bug 82239 - install problems
install problems
Status: CLOSED DUPLICATE of bug 75372
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
7.3
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
http://scripting.topshells.net/anacdu...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-20 05:41 EST by DarkKing
Modified: 2007-04-18 12:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:15 EST
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 DarkKing 2003-01-20 05:41:29 EST
The installer stops and i get an error.. Need help..
Comment 2 Jeremy Katz 2003-01-22 01:02:26 EST

*** This bug has been marked as a duplicate of 75372 ***
Comment 3 marc wissman 2003-01-28 16:10:40 EST
This is not resolved as a duplicate bug.

I ran the linux mediacheck and it passed.

I downloaded a new valhalla 7.3 disk 1 and it passed md5sum check.
I burnt it to cd at 1X speed.

I get the same resulting failure.

Bug 75372 has no additional comments with regards to resolution
other than running mediacheck or that the media and device are
not compatible.

I have tried both SCSI and IDE DVDRoms, IDE CDRom, both IDE and SCSI
target HDD's. From my end it looks to be hardware independent. 

Do you have any suggestions with regards to hacking isys.py that 
anaconda uses. Is there a path that i can hack to possibly find 
the necessary python files on my floppy disk or detachable usb drive?
My initial thought was to add an additional wait 
state when calling the "umount" function. or possibly try to catch
the thrown SystemError (device or resource busy) and retry.
Comment 4 Red Hat Bugzilla 2006-02-21 13:51:15 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.