Bug 479543

Summary: installer does not find a fedora disk after media verification
Product: [Fedora] Fedora Reporter: Michael Ploujnikov <ploujj>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 10CC: anaconda-maint-list
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-14 19:06:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
install disk boot menu
none
install booting messages
none
media test option
none
media test confirmation
none
media check in progress
none
successfully verification dialog
none
additional media dialog
none
error message
none
tty3 content after the first occurance of the disc not found error
none
tty4 content after the first occurance of the disc not found error none

Description Michael Ploujnikov 2009-01-11 00:30:41 UTC
Description of problem:
After performing a disk check on the Fedora installation disk using the installer's console utility fedora keeps telling me: "The fedora disk was not found in any of your cdrom drives" even though the disk check succeeded and I left the same disk in the drive.

Version-Release number of selected component (if applicable):
Fedora-10-x86_64-DVD.iso f1e5ae7db6a1ba227de7294c4112385922388648 sha1sum
I've also noticed this problem with earlier Fedora versions and on different machines.

How reproducible:
Always.

Steps to Reproduce:
1. insert the install disk into the cd/dvd drive
2. reboot computer
3. boot from the dvd
4. select "OK" and "Test" to test the media
5. select "OK" to accept the successful verification of the media
6. select "Skip" because there are no more disks left
  
Actual results:

The console application displays a message box saying:
"The fedora disk was not found in any of your cdrom drives"
Selecting the "OK" button on this message box results in the same message appearing after a bit of disk spinning.

Expected results:
The installation should continue past the console interface into the GUI part.

Additional info:
The CD/DVD drive in the latest machine which exhibited this bug is show as "HL-DT-ST DVD-RAM GSA-H55L 1.00 PQ: 0 ANSI: 5" in dmesg. Its brand is LG.

(I'm just guessing that this is an anaconda bug. I don't know what the console application/component is called).

I was just able to re-produce this problem inside qemu with the DVD's image.

Comment 1 Andy Lindeberg 2009-01-12 15:40:08 UTC
Is this still happening with rawhide?

Comment 2 Michael Ploujnikov 2009-01-12 16:21:51 UTC
How can I check that? Where can I get a rawhide CD/DVD iso?
Can't you check that yourself? I mentioned that I was able to reproduce this with qemu, so the problem shouldn't be related to my hardware.

Comment 3 Andy Lindeberg 2009-01-12 18:47:17 UTC
We have tested it ourselves, and it works perfectly fine for us (see Bug 375011 if you want the long, tortured history of this bug). It works fine for us in F10 too, so I wouldn't trust our hardware to give us the true story.

You can get a rawhide boot.iso from one of the public mirrors: http://mirrors.fedoraproject.org/publiclist

Comment 4 Michael Ploujnikov 2009-01-13 03:52:34 UTC
I was able to to reproduce this problem with a boot.iso from http://fedora.mirror.iweb.ca/development/x86_64/os/images/boot.iso:

$ sha1sum boot.iso 
9c1b6924f95d32d910a7b12c94332f6886cfa02c  boot.iso
$ qemu-system-x86_64 -m 300 -cdrom boot.iso -boot d
Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory

I'm going to attach some screenshots to illustrate what I saw.

I tried pressing "OK" at various time intervals without success.

By the way, I'm running the following version of Qemu:
qemu.x86_64 0.9.1-6.fc9

Comment 5 Michael Ploujnikov 2009-01-13 03:53:38 UTC
Created attachment 328821 [details]
install disk boot menu

Comment 6 Michael Ploujnikov 2009-01-13 03:54:18 UTC
Created attachment 328822 [details]
install booting messages

Comment 7 Michael Ploujnikov 2009-01-13 03:55:31 UTC
Created attachment 328823 [details]
media test option

At this screen I pressed Enter to activate the "OK" button.

Comment 8 Michael Ploujnikov 2009-01-13 03:56:22 UTC
Created attachment 328824 [details]
media test confirmation

At this screen I pressed Enter to activate the "Test" button.

Comment 9 Michael Ploujnikov 2009-01-13 03:56:56 UTC
Created attachment 328825 [details]
media check in progress

This screen just shows that the media was being tested.

Comment 10 Michael Ploujnikov 2009-01-13 03:57:42 UTC
Created attachment 328826 [details]
successfully verification dialog

At this screen I pressed Enter to activate the "OK" button.

Comment 11 Michael Ploujnikov 2009-01-13 03:58:33 UTC
Created attachment 328827 [details]
additional media dialog

At this screen I pressed the right arrow to select the "Continue" button. Then I pressed Enter to activate that button.

Comment 12 Michael Ploujnikov 2009-01-13 04:00:29 UTC
Created attachment 328828 [details]
error message

After pressing the "Continue" button and waiting a few seconds I received this message. Before pressing Enter to activate the "OK" button I checked the other virtual consoles for messages.

Comment 13 Michael Ploujnikov 2009-01-13 04:03:32 UTC
Created attachment 328829 [details]
tty3 content after the first occurance of the disc not found error

Comment 14 Michael Ploujnikov 2009-01-13 04:04:04 UTC
Created attachment 328830 [details]
tty4 content after the first occurance of the disc not found error

Comment 15 Michael Ploujnikov 2009-01-13 13:51:21 UTC
I should mention that subsequent presses of the "OK" button on new copies of the error message window resulted in the last line on tt3 ("ejecting /dev/sr0") being repeated.

Comment 16 Andy Lindeberg 2009-01-13 22:30:48 UTC

*** This bug has been marked as a duplicate of bug 375011 ***

Comment 17 Michael Ploujnikov 2009-01-14 00:03:22 UTC
This isn't fixed yet.

Comment 18 Andy Lindeberg 2009-01-14 19:06:09 UTC
No, it is not, but it's a duplicate of the earlier bug.

*** This bug has been marked as a duplicate of bug 375011 ***