Greetings
I’m no longer able to open the CD/DVD tray. There is an audio CD inside that has been playing fine,
but now no media in the tray is recognized. I just cant find any way to open it.
# eject
eject: unable to find or open device for: `/dev/cdrom'
# eject -v
eject: using default device `/dev/cdrom'
eject: device name is `/dev/cdrom'
eject: unable to find or open device for: `/dev/cdrom'
# eject -t
eject: unable to find or open device for: `/dev/cdrom'
# eject -n
eject: unable to find or open device for: `/dev/cdrom'
# ls -l /dev/cd*
ls: cannot access /dev/cd*: No such file or directory
# ls -l /dev/sr*
brw-rw----+ 1 root disk 11, 0 Apr 17 15:52 /dev/sr0
# ls -l /dev | grep '\->'
lrwxrwxrwx 1 root root 4 Apr 17 15:52 XOR -> null
lrwxrwxrwx 1 root root 11 Apr 17 15:52 core -> /proc/kcore
lrwxrwxrwx 1 root root 3 Apr 17 15:52 fb -> fb0
lrwxrwxrwx 1 root root 13 Apr 17 15:52 fd -> /proc/self/fd
lrwxrwxrwx 1 root root 3 Jul 2 13:01 par0 -> lp0
lrwxrwxrwx 1 root root 4 Apr 17 15:52 root -> dm-1
lrwxrwxrwx 1 root root 4 Apr 17 15:52 rtc -> rtc0
lrwxrwxrwx 1 root root 3 Apr 17 15:52 scd0 -> sr0
lrwxrwxrwx 1 root root 15 Apr 17 15:52 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root root 15 Apr 17 15:52 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root root 15 Apr 17 15:52 stdout -> /proc/self/fd/1
# /usr/sbin/hwinfo --cdrom
20: SCSI 00.0: 10602 CD-ROM (DVD)
[Created at block.247]
UDI: /org/freedesktop/Hal/devices/storage_model_DVD_ROM_DDU1615
Unique ID: KD9E.WjV9fxCiOH8
Parent ID: 3p2J.u9sHtYaOdV0
SysFS ID: /class/block/sr0
SysFS BusID: 0:0:0:0
SysFS Device Link: /devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0
Hardware Class: cdrom
Model: "SONY DVD-ROM DDU1615"
Vendor: "SONY"
Device: "DVD-ROM DDU1615"
Revision: "FDS1"
Driver: "ata_piix", "sr"
Driver Modules: "ata_piix"
Device File: /dev/sr0 (/dev/sg0)
Device Files: /dev/sr0, /dev/scd0, /dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:0:0
Device Number: block 11:0 (char 21:0)
Features: DVD
Drive status: no medium
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #13 (IDE interface)
Drive Speed: 48
# 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
# eject /dev/scd0
eject: unable to eject, last error: Inappropriate ioctl for device
# ls -l /dev/scd0 /dev/sg0
lrwxrwxrwx 1 root root 3 Apr 17 15:52 /dev/scd0 -> sr0
crw-rw----+ 1 root disk 21, 0 Apr 17 15:52 /dev/sg0
# ls -l /dev/sr*
brw-rw----+ 1 root disk 11, 0 Apr 17 15:52 /dev/sr0
# strace -e ioctl eject -r /dev/sr0
ioctl(3, CDROMEJECT, 0x804bb20) = -1 EIO (Input/output error)
eject: unable to eject, last error: Input/output error
# lsof /dev/sr0
# lsof /dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:0:0
On 07/03/2012 02:36 PM, durque wrote:
> Any ideas?
both of your listed machines are running unsupported, past end-of-life
software and have not been security patched since January 14th 2011, for
the 11.1, and January 20th 2012, for 11.3 (unless you have moved it to
Evergreen? see: http://tinyurl.com/4aflkpy) and you should (imo, which
is not shared by every individual here) not connect either to insecure
networks…(like the internet)…so, you should seriously consider
moving to a security patch supported version (currently 11.4 and 12.1)…
or maybe move to longer lived software, like SUSE Linux Enterprise, Red
Hat Enterprise, CentOS or many others…
now, to that drive eject problem: maybe the drive has failed? they do
you know…some in six months, some i six years…(most by six years,
i’d guess)
sure sounds like a hardware problem to to me…that is, the drive itself
is reporting “no medium”…while you say there IS a disk inserted,
which equals hardware problem to me…
see, the drive itself has a circuit board with built in chips/etc to
sense and control all the stuff…sounds to me like it can’t even tell
if there is a disk in the drive…
but, before you rush out to buy a new one:
wait for a better opinion (i have been wrong before…even today)
Durqu, look closely at the CD/DVD-ROM drive and below the drive tray and on the right side is a tiny hole. With the computer powered off, take a paper clip that you have made straight and push it through that hole very straight. Go very slow, go very straight but firmly and this will push the CD Tray open. Once it is out a 1/4 inch or so, you can use your fingers to pull it out the rest of the way. When a CD tray does not open after repeated attempts and always after you did a system restart and a power down as well to make sure it was not just a software problem, likely means there is hardware problem. A stuck CD can be caused by a CD label coming off, which can be bad, due to the hardware sticking and perhaps from an electronic failure. Normally, unless you can identify the issue and fix it and if it occurs more than once, take it as time to replace your CD or DVD-ROM drive with a newer and faster model. The issue is more problematic with laptop drives in finding a replacement, but they are less prone to a mechanical lockups however. Look for that hole and give my advice a try.
Thank’s for insight and comments regarding my problem. I’m quite confident that the problem will resolve itself with either a reboot or the paper clip trick.
The thing is, been accustomed to Linux, I kind of assumed there would be a software solution to my problem. I suspect that there might be something to do with killing a process, daemon, restarting udev or something.
Any idea to a software approach that does’nt require a reboot?
Am 04.07.2012 14:46, schrieb durque:
> Any idea to a software approach that does’nt require a reboot?
You could try to eject it as root and giving it the precise device
su -c "eject /dev/sr0"
if it fails repeat it several times. If you are very lucky it works.
If it is something mechanical of course it will not do anything or if a
process with sufficient strong rights blocks it.
–
PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
Am 04.07.2012 14:58, schrieb Martin Helm:
> Am 04.07.2012 14:46, schrieb durque:
>> Any idea to a software approach that does’nt require a reboot?
> You could try to eject it as root and giving it the precise device
>
> su -c "eject /dev/sr0"
>
> if it fails repeat it several times. If you are very lucky it works.
> If it is something mechanical of course it will not do anything or if a
> process with sufficient strong rights blocks it.
>
Sorry forget it I see your prompt was #, you already did it as root.
–
PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
Bringing this topic to an end, I rebooted (“real reboot”) and to no surprise the CD/DVD tray opened when starting up again. I’ve made notice of the fastreboot script, and will try that on another occasion. Thanks for the tip.
Well its good to know only a reboot was all that was required and so the CD/DVD just needed to be reset to get it working again. We were happy to help and let us know if you need any other assistance.