Bug 473482 - No opportunity to remove DVD before firstboot
Summary: No opportunity to remove DVD before firstboot
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 12
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Martin Sivák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 475036 476458 477617 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-28 19:24 UTC by John J. McDonough
Modified: 2010-12-05 07:05 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-05 07:05:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John J. McDonough 2008-11-28 19:24:37 UTC
Description of problem:
At end of installation, the DVD is not ejected, and in fact is locked.  the user must recognize the need to eject the DVD during POST.  On a system that gets through POST quickly, this could get annoying.  For a new user, thinking he had a successful install and then starting install over again could be confusing.

Version-Release number of selected component (if applicable):
F10 preview through GA (may have also been on beta, it may have been alright on alpha but that seems like a long time ago).

How reproducible:
always

Steps to Reproduce:
1. Boot from installation DVD
2. Go through installation
3. Observe no way to remove DVD before reboot
  
Actual results:
Push to reboot

Expected results:
DVD ejected, user admonished to remove installation media before reboot

Additional info:

Comment 1 Andre Robatino 2008-11-28 20:29:01 UTC
I did manage to get the disc out during reboot, but the tray started closing immediately after opening, so I only had about 1/2 second and nearly broke the tray doing it.  It's much safer to leave the disc in, restart the install, then when you get to the mediacheck, tell it to eject the disc, take it out, and then Ctrl-Alt-Del to reboot.  This should at least be documented since it's too late to fix.

Comment 2 Chris Lumens 2008-12-02 15:50:00 UTC
We definitely do attempt to eject the DVD once installation is finished, though it could very well still be mounted.  Can you check /var/log/anaconda.syslog and /var/log/anaconda.log on the installed system to see if there are any error messages?

Comment 3 John J. McDonough 2008-12-02 16:13:37 UTC
Nothing suspicious specific to the DVD but at the end of anaconda.syslog there are some suspicious lines:

<7>SELinux:  73 classes, 109076 rules
<6>uno<7>SELinux:  73 classes, 109076 rules
<6>uno.bin[11745]: segfault at 0 ip 00307c7b sp b5bfe0f0 error 6 in libuno_cppu.
so.3[2ed000+2c000]
<6>uno.bin[11897]: segfault at 0 ip 00307c7b sp b5aa70f0 error 6 in libuno_cppu.
so.3[2ed000+2c000]

Comment 4 Andre Robatino 2008-12-02 18:52:08 UTC
I don't see any suspicious in either file, even though I had the same issue during install.  By the way, the installer should not only eject the disc, but also tell the user explicitly to remove the disc, which it doesn't (I think it did in F9, but I might be wrong).

Comment 5 TK009 2008-12-07 21:20:11 UTC
This bug has been triaged

Comment 6 Chris Lumens 2008-12-10 19:36:33 UTC
*** Bug 475036 has been marked as a duplicate of this bug. ***

Comment 7 Vadym Chepkov 2008-12-13 19:32:18 UTC
There is another "bad behavior" I observed using network kickstart intstallation:

if you have in your kickstart

install 
url --url http://path/to/dist/
...
reboot -eject

anaconda crashes when it is trying to eject the disk. I suspect it tries to eject "network DVD" rather then CD I started installation from.

Comment 8 Chris Lumens 2008-12-15 15:01:13 UTC
*** Bug 476458 has been marked as a duplicate of this bug. ***

Comment 9 Chris Lumens 2008-12-23 16:02:33 UTC
*** Bug 477617 has been marked as a duplicate of this bug. ***

Comment 10 Don Hickey 2009-02-22 17:13:13 UTC
I'm getting this message in anaconda.syslog when my system quits responding.

<6>uno.bin[12091]: segfault at 0 ip 0000000000c3eecd sp 00007ff0a2109cb0 error 6 in libuno_cppu.so.3[c24000+2d000]

All I can do is power off/power on and reboot. This is a Fedora 10 system installed for months with all maintenance applied. There is no cd/dvd involved at all.

Any help will be appreciated.

Comment 11 Matthieu Araman 2009-03-30 11:38:56 UTC
seeing this too with rawhide boot.iso 20090326.(so with the new anaconda)
I didn't have any user message during installation saying to remove the cdrom.
There's nothing related to this in /var/log/anaconda.log or /var/log/anaconda.syslog
I guess anaconda didn't even try to eject it ...
Was anaconda lost because the installation is half from cd, half from network ?

Comment 12 Chris Lumens 2009-07-28 20:28:56 UTC
Can you please give this a test with F12 alpha?  Martin committed a patch just the other day that should have fixed this up.  If it's still broken, let's see what new information we can get and make a concerted effort to get this fixed for F12 final.  Thanks.

Comment 13 Paul Howarth 2009-11-10 11:26:44 UTC
Still had this issue with F12 RC4.

Comment 14 Paul Howarth 2009-11-10 14:06:26 UTC
As a further data point, I've just installed F12 RC4 (x86_64) in a KVM virtual machine (F12 host with virt-manager) using the DVD ISO for install media, and at the end of the install where the "Reboot" button is presented, I changed to the "Virtual Hardware Details" tab and clicked "Disconnect" for "Disk hdc" and it couldn't do it:

Error Removing CDROM: operation failed: changing cdrom media failed: eject ide1-cd0 device is locked

I'd have expected that that would be easily reproducible.

Comment 15 Bug Zapper 2009-11-16 09:41:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 16 Dennis 2010-03-13 21:12:04 UTC
I am having this exact same problem with the Fedora 12 CD installation.

I can test all the media, and everything works fine for verify-media.

But during installation, "Please insert Fedora disc 2 to continue" fails.
I'm stuck.

I am willing to attach any logs / commands / etc for testing & resolution purposes.

Concerning hardware, I'm using 2 gigabyte DDRD RAM on a ASUS P5QC motherboard. Intel Dual Core CPU.

The computer has 2 disk drives, a CDRW drive and a DVD drive. I believe these are older models, bought around 2006. Both drives worked flawlessly in Fedora 11.

Thanks to devs (and bug triagers) for their hard work.
Hope this problem gets resolved fast so i can run Fedora 12.

Comment 17 Bug Zapper 2010-11-04 11:39:41 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 18 Bug Zapper 2010-12-05 07:05:24 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


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