Ubuntu

[Dell Inspiron 2500] Can't eject cd rom : Inappropriate ioctl for device

Reported by frenchy82 on 2011-10-16
252
This bug affects 53 people
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Undecided
Unassigned

Bug Description

It's impossible to eject cd rom with the command eject or with the hard button
"Error ejecting: eject exited with exit code 1: eject: unable to eject, last error: Inappropriate ioctl for device"

This is a fresh install of oneiric.
Tried with the udev package from natty and it's working

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: udev 173-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Sun Oct 16 09:45:47 2011
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 0cde:0008 Z-Com XG-703A 802.11g Wireless Adapter [Intersil ISL3887]
MachineType: Dell Computer Corporation Inspiron 2500
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=f98a363b-9676-42d1-ae6a-afa64e3b5081 ro quiet splash pci=noacpi vt.handoff=7
SourcePackage: udev
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2001
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: A11
dmi.board.name: Inspiron 2500
dmi.board.vendor: Dell Computer Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Dell Computer Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrA11:bd12/03/2001:svnDellComputerCorporation:pnInspiron2500:pvrRevisionA0:rvnDellComputerCorporation:rnInspiron2500:rvrNone:cvnDellComputerCorporation:ct1:cvrN/A:
dmi.product.name: Inspiron 2500
dmi.product.version: Revision A0
dmi.sys.vendor: Dell Computer Corporation

frenchy82 (cartes) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in udev (Ubuntu):
status: New → Confirmed
frenchy82 (cartes) wrote :

Do you need more information to look at this problem/bug?

Britt Yazel (bwyazel) wrote :

I now too have this bug. This is the first time this has happened and I am running Precise. I was able to open the drive before, I blanked a disk, and now it s anable to open due to the same error as above

Marco Scannadinari (zheoffec) wrote :

Try this:

Steps:

1. 'sudo eject /dev/sr0'

2. 'file /dev/sr0'

3. 'sudo eject -i off'

(Thanks to Messelink)

ubuntu 11.04 32bit [core2duo]

1. 'sudo eject /dev/sr0'
eject: unable to eject, last error: Inappropriate ioctl for device

2. 'file /dev/sr0'
/dev/sr0: block special

3. 'sudo eject -i off'
CD-Drive may be ejected with device button

no joy

File manager shows blank DVD is still blank.

'sudo growisofs -dvd-compat -Z /dev/dvdrw=/stuff/mint-mate-64.iso'
:-( unable to INQUIRY: Input/output error

Can neither eject blank disc nor burn blank disc [using actual-cdrtools and not borked debian fork].

I would rather NOT need to power cycle the workstation to merely eject a disc. This feels like microsoft masochism. :|

^ 12.04

tags: added: 12.04
joshyg6 (josheg) wrote :

I have this issue, too..

baron_army (baron-army) wrote :

I can report this issue on Mythbuntu 12.04. No attempt to eject disk is successful. Furthermore, the drive unmounts itself while running and then I can eject the disk.

i´m running a fresh installation of 12.04.1 pt-br and i see this bug too.

only after reboot i can use cd/dvd drive again with any other cd/dvd.

tried steps of comment #6 and had the same responses.

Hans Deragon (deragon) wrote :

In my case when it happens, if I press the button of the dvd drive, the bay opens. I close, try 'eject' and then it works.
12.04 here, Lenovo T61P.

LindseyD. (ai279) wrote :

LinuxMint 13 KDE--udev 175-0ubuntu9

Would it be okay to install an earlier version of udev? Has anyone else tried frenchy82's workaround?

Harry Smith (harryat54) wrote :

i use the new ubuntu 12.10 and i still have the same problem.
P
L
E
A
S
E

F
I
X

T
H
I
S

B
U
G

please post an update as to when this bug will be fixed. I have a dvd rom drive that is inoperable. Many thanks.

I beg your pardon, I have just repaired the problem by running eject -i /dev/sr1.

I will most likely add this as an init script.

Many thanks.

Peter M. Clausen (pclausen) wrote :

This only happens for me because of some problem reading a DVD, which I also cannot mount. CD's are mounted, read OK and ejected correctly so drive is in principle OK. RUnning up2date 12.04 64-bit.

Verbose output eject command:

 $ eject -v /dev/sr0
eject: device name is `/dev/sr0'
eject: expanded name is `/dev/sr0'
eject: `/dev/sr0' is not mounted
eject: `/dev/sr0' is not a mount point
eject: `/dev/sr0' is not a multipartition device
eject: trying to eject `/dev/sr0' using CD-ROM eject command
eject: CD-ROM eject command failed
eject: trying to eject `/dev/sr0' using SCSI commands
eject: SCSI eject failed
eject: trying to eject `/dev/sr0' using floppy eject command
eject: floppy eject command failed
eject: trying to eject `/dev/sr0' using tape offline command
eject: tape offline command failed
eject: unable to eject, last error: Inappropriate ioctl for device

ethanay (ethan-y-us) wrote :

Step #3 in comment 5 above works for me:
3. 'sudo eject -i off'

So it seems that the drives are locking after eject for some reason? For me, this happens on Lubuntu 12.10. I can insert one CD and eject it, but then the drive is unusable again until I issue the command above.

It only happens with my DVD reader (/dev/sr0), not my DVD writer (/dev/sr1). lshw taken after issuing the command above, both drives are in fact empty.

 *-scsi:0
          physical id: 1
          logical name: scsi0
          capabilities: emulated
        *-cdrom:0
             description: DVD reader
             product: DVD-ROM GDR8161B
             vendor: HL-DT-ST
             physical id: 0.0.0
             bus info: scsi@0:0.0.0
             logical name: /dev/cdrom
             logical name: /dev/dvd
             logical name: /dev/sr0
             version: 0040
             capabilities: removable audio dvd
             configuration: ansiversion=5 status=nodisc
        *-cdrom:1
             description: DVD writer
             product: DVD-RW GSA-H11N
             vendor: HL-DT-ST
             physical id: 0.1.0
             bus info: scsi@0:0.1.0
             logical name: /dev/cdrom1
             logical name: /dev/cdrw1
             logical name: /dev/dvd1
             logical name: /dev/dvdrw1
             logical name: /dev/sr1
             version: JG03
             capabilities: removable audio cd-r cd-rw dvd dvd-r
             configuration: ansiversion=5 status=nodisc

James (jamesphipps2000) wrote :

I can confirm this issue with ubuntu 12.04 LTS. I have a standard cd rom drive (no burner or dvd). I had also seen this issue with the previous LTS release of ubuntu. The drive seems to eject fine until it completes its initial intialization. I have ejected the tray serveral times, until it will not eject anymore and it seems to stop ejecting after the light stops blinking on the drive. After login i try the eject command and get the unable to eject, last error: Inappropriate ioctl for device error. I can force the drive trat open, insert a disk (gparted livecd), close the tray with the button as normal, the system opens the disk fine. With the disk in the closed tray the eject command returns no error,remove the disk and close the tray and the issue returns including the the eject command errors. Any additional data needed let me know.

Ejdesgaard (ejdesgaard) wrote :

I encountered this problem by doing the following on 12.04 64bit:
1. Start burning of iso via brasero, where I enabled "simulated"
2. while the simulation ran, I found out that a new release was released and I wanted to use the new iso, so i canceled the burning, while brasero was still simulating.
3. When I tried to burn the new iso, brasero couldn't eject the cdrom drive.

Fix:
The following fix from James Stewart Miller (jamesstewartmiller) worked.
sudo eject -i off /dev/cdrom fixed the problem for me.

Jim K (jimofadel) wrote :

I found the same problem on 12.04; I think it started when I was using Rythm Box to "extract" some music from a CD, and when I saw that it was creating .ogg files, I decided to terminate the job, and finding there was no "cancel" button in the application, I pushed the eject button on the cd drive, admittedly a brash act. The drive did open, but the application hung, and something had changed irreversibly. The problem still persists now as soon as I boot up I can open the drive with the button once, but after that, there is nothing that will open it except a reboot, or the terminal command "sudo eject -i off", which does not eject, but re-enables the button on the drive. I have been really pleased with 12.04; this is the first shortcoming that I have found that was significant to me.

Today it hit me again on 12.04: See also Bug #986845.

michael@quad:~$ eject
eject: unable to eject, last error: Inappropriate ioctl for device

tags: added: precise
Geoff (palmerg) wrote :

This is happening in 13.04 too.

Part of the problem seems to be its intermittent nature. A combination of button presses and eject commands eventually opens the drive (at least in my case).

Comment #5 didn't work for me. (I got the same results listed in comment #6.) Then I tried "sudo eject -i off" again and it opened when I pressed the button.

One observation: this only seems to happen when the drive is empty. If there's a disc in it, it pops open happily.

tags: added: quantal raring
removed: 12.04
Andrey (aol-nnov) wrote :

Just stumbled upon such a problem. I was installing an OS onto VM using host cdrom. Installation programm locked the drive and did not unlock it afterwards for some reason, so, executing eject on the host system yields "Inappropriate ioctl for device" error

sudo eject -i0
and then
sudo eject
resolved my issue. The drive bay opened automatically after last command - i hadn't to push the hw button to eject.

Bkorb (bkorb) wrote :

I guess different folks have different results.
My version of "eject" does not accept "-i", but uses "-a" instead:

> # eject -a0
> eject: CD-ROM auto-eject command failed: Device or resource busy

Thus:

> # eject -v
> eject: using default device `/dev/cdrom'
> eject: device name is `/dev/cdrom'
> eject: expanded name is `/dev/cdrom'
> eject: `/dev/cdrom' is a link to `/dev/sr0'
> eject: `/dev/sr0' is not mounted
> eject: `/dev/sr0' is not a mount point
> eject: `/dev/sr0' is not a multipartition device
> eject: trying to eject `/dev/sr0' using CD-ROM eject command
> eject: CD-ROM eject command failed
> eject: trying to eject `/dev/sr0' using SCSI commands
> eject: SCSI eject failed
> eject: trying to eject `/dev/sr0' using floppy eject command
> eject: floppy eject command failed
> eject: trying to eject `/dev/sr0' using tape offline command
> eject: tape offline command failed
> eject: unable to eject, last error: Inappropriate ioctl for device
> # lsof /dev/sr0
> #

so for me, rebooting is the only answer I can find.

Eliah Kagen / Andrey / Bkorb, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

summary: - can't eject cd rom : Inappropriate ioctl for device
+ [Dell Inspiron 2500] Can't eject cd rom : Inappropriate ioctl for device

frenchy82, the issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Saucy Salamander. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://cdimage.ubuntu.com/daily-live/current/ . Thanks again and we appreciate your help.

tags: added: bios-outdated-a15 needs-upstream-testing regression-potential
removed: precise quantal raring
tags: added: regression-release
removed: regression-potential
Changed in udev (Ubuntu):
status: Confirmed → Incomplete
LindseyD. (ai279) wrote :

I just tried with LinuxMint 15 on a USB stick and the problem persists. Has anyone found a solution that doesn't require upgrading one's entire system?

Maurice McCarthy (manselton) wrote :

Lindsey, I have an Uberstudent installation (modified Xubuntu raring) the same fault has occurred for me after ripping some dvds.

# sudo eject -i off

as first given above by Marco Scannadenari works for me. Then both pressing the manual eject button or typing eject work. It is at least a fast work-around. Quite why it is happening I don't know.

Maurice McCarthy (manselton) wrote :

Archlinux appear to have fixed a similar fault 2 years ago, most of the work was taken from Fedora but they had to further patch it themselves. (Apologies I'm not a programmer so I can only give pointers not fixes.)

LindseyD. / Maurice McCarthy, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

LindseyD. (ai279) wrote :

Apologies for the delay in replying. I have to say, all this is a nightmare on dialup. Launchpad alone can take up to 5 minutes to load.

I managed to track down the Natty udev, but it requires the upgrade/installation of 24 dependencies--too much of a risk of breaking something else for me to try it. Same with installing another kernel. (And if the problem's in udev, why change the kernel?)

Maurice, as I understand it # means you're already root so I don't quite understand # sudo eject -i off. However, I su'd into root and tried # eject -i off and it worked, but only once :-(

I will not be opening a new report, because a) Linux Mint isn't on the dropdown list of "affects other distributions" and b) because I have no idea now whether it's a udev bug or a kernel bug and c) all the report would say is, see bug 875543 for details. I haven't got the resources in terms of spare computers or high speed internet access to pursue this on my own. The only reason I posted above was, the bug was set to expire unless someone said something. However, if anyone else has the physical and emotional resources to open a new report, I'd like to know about it.

Launchpad Janitor (janitor) wrote :

[Expired for udev (Ubuntu) because there has been no activity for 60 days.]

Changed in udev (Ubuntu):
status: Incomplete → Expired
damgut (damgut) wrote :

I have this problem after updating from ubuntu 10.04 to 12.04

# not possible to execute "eject" command using option "-T" or "-r" if a cd is available into the tray:
ioctl(14, CDROMEJECT, 0) = -1 EIO (Input/output error)

# this command solve the problem:
eject -i off /dev/cdrom

# As a Workarround I've added this line to my cron job:
*/5 * * * * eject -i off /dev/cdrom

damgut, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers