Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 569377
Summary: | CDROM install unable to eject disc - storage: error ejecting cdrom sr0: (5, 'Input/output error') | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> | ||||
Component: | anaconda | Assignee: | Peter Jones <pjones> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 13 | CC: | jonathan, jturner, vanmeeuwen+fedora | ||||
Target Milestone: | --- | Keywords: | CommonBugs | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | https://fedoraproject.org/wiki/Common_F13_bugs#failure-to-eject-cdrom | ||||||
Fixed In Version: | anaconda-13.37-1.fc13 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-03-27 04:53:50 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 538274 | ||||||
Attachments: |
|
Description
James Laska
2010-03-01 13:34:26 UTC
= Additional information = From tty2, I can successfully eject the disc by typing: # eject /dev/cdrom = Tested workaround = 1) change to tty2 2) type: eject /dev/cdrom 3) insert next disc 4) type: mount -o ro /dev/cdrom /mnt/source 5) Return to tty6 6) Select OK to proceed with install NOTE: step#4 was required, for some reason anaconda wouldn't continue the install unless I manually mounted the next ISO What about if you flip to tty2 and instead:
PYTHONPATH=/usr/lib/anaconda python
>>> import _isys
>>> import os
>>> fd = os.open("/dev/sr0", os.RD_ONLY|os.NONBLOCK)
>>> _isys.ejectcdrom(fd)
Figures, when retesting ... the problem did not occur. I'll continue testing ... Reproduced, the problem surfaces only when you mediacheck the disc in loader. The suggestion in comment#3 does not resolve the issue. >>> _isys.ejectcdrom(fd) Traceback (most recent call last): File "<stdin>", line 1, in <module> SystemError: (5, 'Input/output error') Well, the point of the suggestion in comment #3 was to isolate that it was the same code anaconda's using that causes the problem without involving all of anaconda. Moving to F13Beta per point#3 of the Beta release criteria (https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria#Beta_Release_Requirements) Documented known issue and workaround for Alpha users at https://fedoraproject.org/wiki/Common_F13_bugs#failure-to-eject-cdrom James,
I've taken a quick look at what the eject command does differently,
Can you try some python code on tty2 again, but this time this one:
PYTHONPATH=/usr/lib/anaconda python
>>> import _isys
>>> import os
>>> fd = os.open("/dev/sr0", os.O_RDWR|os.O_NONBLOCK)
>>> _isys.ejectcdrom(fd)
And can you also run eject in verbose mode:
eject -v /dev/sr0
Thanks,
Hans
Hans - I already asked him to do that. Please see comment #3 and comment #5. (In reply to comment #10) > Hans - I already asked him to do that. Please see comment #3 and comment #5. Chris, Look closer: 1) My python code has other open flags (the same as the eject binary uses) 2) The eject command I gave has a "-v" James, Could you please provide the info I requested in comment #9. Note that it would be good to have the output of both when booted with and without mediacheck. Thanks, Hans (In reply to comment #11) > (In reply to comment #10) > > Hans - I already asked him to do that. Please see comment #3 and comment #5. > > Chris, > > Look closer: > 1) My python code has other open flags (the same as the eject binary uses) > 2) The eject command I gave has a "-v" > > James, > > Could you please provide the info I requested in comment #9. Note that it would > be good to have the output of both when booted with and without mediacheck. Due to further hal-ectomy changes during the F-13-Alpha release process, the bits released as F-13-Alpha no longer have the 'eject' binary available. I have copied the /usr/sbin/eject binary from the F13 eject package and run it on the system. = with mediacheck = # eject -v -v -v /dev/cdrom /tmp/eject: device name is `/dev/cdrom' /tmp/eject: expanded name is `/dev/cdrom' /tmp/eject: `/dev/cdrom' is a link to `/dev/sr0' /tmp/eject: `/dev/sr0' is mounted at `/mnt/source' /tmp/eject: checking if device "/dev/sr0" has a removable or hotpluggable flag /tmp/eject: unmounting device `/dev/sr0' from `/mnt/source' /tmp/eject: `/dev/sr0' is not a multipartition device /tmp/eject: trying to eject `/dev/sr0' using CD-ROM eject command /tmp/eject: CD-ROM eject command failed /tmp/eject: trying to eject `/dev/sr0' using SCSI commands /tmp/eject: SCSI eject succeeded = without mediacheck = # eject -v -v -v /dev/cdrom /tmp/eject: device name is `/dev/cdrom' /tmp/eject: expanded name is `/dev/cdrom' /tmp/eject: `/dev/cdrom' is a link to `/dev/sr0' /tmp/eject: `/dev/sr0' is not mounted /tmp/eject: unable to open /etc/fstab: No such file or directory /tmp/eject: checking if device "/dev/sr0" has a removable or hotpluggable flag /tmp/eject: `/dev/sr0' is not a multipartition device /tmp/eject: trying to eject `/dev/sr0' using CD-ROM eject command /tmp/eject: CD-ROM eject command succeeded Moving this over to pjones as discussed on irc. Retested and confirmed the reported behavior remains present in F-13-Beta-TC1 anaconda-13.37-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.37-1.fc13 anaconda-13.37-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |