Bug 82514 – exception ocurred during installation of Red Hat Linux 8 IOError:[Errno 5} Input/output error

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 82514 - exception ocurred during installation of Red Hat Linux 8 IOError:[Errno 5} Input/output error

Summary:	exception ocurred during installation of Red Hat Linux 8 IOError:[Errno 5} In...

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Public Beta
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	phoebe
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael Fulbright
QA Contact:	Mike McLean
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-01-22 18:01 EST by angel ferrer
Modified:	2007-04-18 12:50 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-01-29 16:59:27 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description angel ferrer 2003-01-22 18:01:29 EST

Description of problem:
exception ocurred during installation of Red Hat Linux 8 IOError:[Errno 5} Input/output error
during installation of package flex-2.5.4a-26

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


How reproducible:
start installtion again

Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:

Comment 1 Michael Fulbright 2003-01-23 10:54:34 EST

Have you checked you media (see bug 75008)?

Comment 2 angel ferrer 2003-01-24 10:18:06 EST

The behavior described above happened three times in a row. That is why we 
reported it as a bug. 

However, a fourth try a few hours later, while demonstrating it to someone else, 
the exception did not occur and the installation ran to completion successfully 
and satisfactorily. 

Michael F. (see comment above) may have been right that it was media problem, 
possibly marginal. In any event, we have not been able to reproduce it after 
those first initial three tries. Sorry about the false alarm

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