Bug 153014

Also a problem with FC2.  Appears to be a bug with the cd-roms on certain IBM
systems not just the servers.

An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

I have tried Fedora Core 4 - it has the same problem on mentioned hardware.

does booting with acpi=off make any difference ?

No, it doesn't.

http://fedora.isphuset.no/ contains an unofficial Fedora 4.1, which may get you
up and running, as it has a install kernel based on one of the errata kernels.

The problem still exists in 4.1. 

The message from 4th console contains slighly more details:

<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
<3>ATAPI device hdc:
<4>  Error: Medium error -- (Sense key=0x03)
<3>  (reserved error code) -- (asc=0x02, ascq=0x00)
<3>  The failed "Read 10" packet command was:
<4>  "28 00 00 00 00 10 00 00 01 00 00 00 00 00 00 00 "
<4>end_request: I/O error, dev hdc, sector 64
<4>isofs_fill_super: bread failed, dev=hdc, iso_biknum=16, block=16

booting with ide=nodma worked for me on an IBM NetVista.

Without option:

- No media check
- Remains in textmodus.
- choose language
- choose keyboard
- "Fedore Core CD not found..."

With option:
- Media check
- Starts graphical installation.
- OK.

I confirm, that "ide=nodma" option works for IBM xSeries 205 as well. 
It seems this problem is related to DMA.

2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.

Due to the overhead involved in creating new ISOs (which is what would be
required for fixing bugs seen at installation time that don't have workarounds),
this bug has been closed.

For more information and suggestions, please see bug 169613

Thanks.

The problem still exists in Fedora Core 5.

Same problem here on Core 4 and Core 5. I have an IBM 8668-44X eServer.

Same problem here on Core 5, ide=nodma doesn't fix it.

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

If you let me know how to alter a kernel on FC5 bootable installation CD - I 
will do that, otherwise I will wait for a new FC (pre)release and will retest 
it then.

Thank you.

The Fedora Unity project (www.fedoraunity.org) does respins of older releases
with newer kernels from time to time. If this did get fixed, then its possible
that media will work for you.

Created attachment 142966 [details]
Screenshot of 4th console of Fedora Core 6

Fedora Core 6 still has the same problem. I have attached a screenshot of 4th 
console. As mentioned above, it boots fine with "ide=nodma" option.

Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Impossible to test, since FC8 is currently distributed on DVD media, while
specific servers have CDROM's with no DVD compatibility.

Please, close this ticket.