Bug 187159 - Failed Fedora/RPMS/xpdf-3.01-12.1.i386.rpm in xpdf
Failed Fedora/RPMS/xpdf-3.01-12.1.i386.rpm in xpdf
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
5
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-28 16:48 EST by Ben
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-03-28 16:53:35 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)
anaconda dump (677.16 KB, text/plain)
2006-03-28 16:48 EST, Ben
no flags Details

  None (edit)
Description Ben 2006-03-28 16:48:53 EST
Description of problem:

Failed Fedora/RPMS/xpdf-3.01-12.1.i386.rpm in xpdf

Install fails with IO error and complains about xpdf-3.01-12.1.i386.rpm in xpdf

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


How reproducible:

Not sure
Steps to Reproduce:
1. perform upgrade install from FC4 to FC5 
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Ben 2006-03-28 16:48:53 EST
Created attachment 126939 [details]
anaconda dump
Comment 2 Chris Lumens 2006-03-28 16:53:35 EST
Your traceback log indicates errors reading from the drive:

<4>hdc: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
<4>hdc: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
<4>ide: failed opcode was: unknown
<4>hdc: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
<4>hdc: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
<4>ide: failed opcode was: unknown
<4>end_request: I/O error, dev hdc, sector 1402688

The traceback you ran into in this error path has been fixed in Rawhide, but the
underlying problem here is either your media, your reader, or the combination of
the two.

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