Red Hat Bugzilla – Bug 496183
F11 Beta: anaconda kickstart install quits - The Fedora disc was not found in any of your CDROM drives.
Last modified: 2010-06-28 07:52:09 EDT
Description of problem:
Booted F11 Beta DVD (x86_64) with kickstart file on usbkey. It found the kickstart file and then showed this error:
The Fedora disc was not found in any of your CDROM drives. Please insert the Fedora disc and press OK to retry.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot F11 Beta DVD (x86_64) with kickstart on usbkey.
My CD/DVDROM drive is LITE-ON LH20A1H.
When the installer first starts it does not find the usbkey right away. It put it on a different device than when it was mounted in the system. So I guessed a couple devices and the installer found it. After that the error occurs.
Now, if I guess the device correctly on the kernel line then the installation will proceed and it reads the DVD.
Just a guess. This may be related to other CDROM issues where if the CDROM drive spins down then the kernel can no longer read the CDROM. Sometimes when these problems occur if I eject/reload the CDROM then things can proceed. The kernel is not spinning the drive back up before trying to read the medium after a delay long enough for the drive to spin down.
What sorts of error messages do you see on tty3 and tty4?
I didn't look at the time and I'm a little hesitant to rerun this test because after one of these runs with the usbkey we noticed that anaconda had knocked out an array element in our raid-5 array as I mentioned in one of the other bugs I filed.
Oh I just noticed this myself. It appears the problem here is related to media check.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Chris, here are the errors mssgs u requested above:
WARNING: error ejecting cdrom sr0: (5, 'Input/output error')
INFO: set SELinux context for mountpoint /mnt/source to system_u:object_r:mnt_t:s0
INFO: set SELinux context for newly mounted filesystem root at /mnt/source to system_u:object_r:mnt_t:s0
<7>SELinux: initialized (dev sr0, type iso9660), uses genfs_contexts
<6>sr 6:0:0:0: [sr0] Unhandled sense code
<6>sr 6:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
<6>sr 6:0:0:0: [sr0] Sense Key : Medium Error [current]
<6>sr 6:0:0:0: [sr0] Add. Sense: No seek complete
<3>end_request: I/O error, dev sr0, sector 64
<4>isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
note: some of the error output might be fat fingered
note: I'm installing fc12, using Sony SATA cdrom <--> usb
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.