eject: unable to eject, last error: Inappropriate ioctl for device

[mdmcginn]

See Bug #875543

michael@doulos:~$ eject /dev/sr0
eject: unable to eject, last error: Inappropriate ioctl for device
michael@doulos:~$ sudo eject -i off
eject: tried to use `/media/cdrom' as device name
michael@doulos:~$ file /dev/sr0
/dev/sr0: block special (11/0)
michael@doulos:~$ sudo eject -i off
[sudo] password for michael:
eject: tried to use `/media/cdrom' as device name but it is no block device
eject: unable to find or open device for: `cdrom'
michael@doulos:~$ eject -i off /dev/sr0
ioctl on CDROM_LOCKDOOR: Device or resource busy
michael@doulos:~$ ls /media
cdrom michael

michael@doulos:~$ sudo lshw
SCSI
(Still waiting for further response here)

Probable cause: As I was creating a traditional music CD using Brasero, I renamed the containing folder while the first song was being written... Error messages resulted. The hard drive ran for a long while. After that, the CD light has been on all night, and I think it's still quietly running. Pressing and holding the CD release button didn't work. I haven't tried sticking a paper clip into the hole. The drive is not visible in Thunar file manager.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-28-generic 3.16.0-28.38
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic i686
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michael 3339 F.... pulseaudio
CurrentDesktop: XFCE
Date: Fri Dec 19 05:19:27 2014
HibernationDevice: RESUME=UUID=48a513bd-893a-4888-8179-ab39991a217c
InstallationDate: Installed on 2010-10-21 (1519 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
IwConfig:
 lo no wireless extensions.

 eth2 no wireless extensions.
MachineType: Dell Inc. OptiPlex 760
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=2d538d30-263b-48c6-9250-81f4004b1215 ro vga=789 plymouth:debug quiet drm.debug=0xe splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-28-generic N/A
 linux-backports-modules-3.16.0-28-generic N/A
 linux-firmware 1.138
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-10-31 (48 days ago)
dmi.bios.date: 08/17/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0M863N
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/17/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M863N:rvrA01:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 760
dmi.sys.vendor: Dell Inc.

[mdmcginn (mcweb)]

Relevant result of sudo lshw:
        *-cdrom
             description: DVD-RAM writer
             product: BD ROM BC-5501H
             vendor: hp
             physical id: 0.0.0
             bus info: scsi@3:0.0.0
             logical name: /dev/sr0
             version: 2.87
             capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
             configuration: ansiversion=5 status=ready
           *-medium
                physical id: 0
                logical name: /dev/sr0

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

mdmcginn, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product-support/product/optiplex-760/drivers an update to your computer's buggy and outdated BIOS is available (A16). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

[mdmcginn (mcweb)]

No further problems.

[penalvch (penalvch)]

mdmcginn, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404199/comments/4 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Andrea Croci (andrea.croci)]

Just for what it's worth, I recently had the same problem and it turned out to be a faulty SATA data cable. People affected by this error message may want to check on that before filing bug reports or buying new drives.