I have an old cdrom drive that I would like to use with the eject program. Anyways it works on all my newer devices, but the 'eject -t' command does not always work with my TOSHIBA CD-ROM XM-6102B. I say "doesn't always" because it works if I eject a mounted disc and then execute 'eject -t'. It works even if I switch discs. It gives the following error if I eject an unmounted disc and then 'eject -t', or if I 'eject -t' an empty tray. /*EXAMPLE*/ //eject mounted disc (doesn't matter if I keep the same disc in when I eject -t # eject -v /dev/hdd eject: device name is `/dev/hdd' eject: expanded name is `/dev/hdd' eject: `/dev/hdd' is mounted at `/media/cdrom' eject: unmounting `/dev/hdd' eject: `/dev/hdd' is a multipartition device eject: trying to eject `/dev/hdd' using CD-ROM eject command eject: CD-ROM eject command succeeded # eject -vt /dev/hdd eject: device name is `/dev/hdd' eject: expanded name is `/dev/hdd' eject: `/dev/hdd' is not mounted eject: `/dev/hdd' is not a mount point eject: closing tray //eject with unmounted disc or empty tray # umount /dev/hdd # eject -v /dev/hdd eject: device name is `/dev/hdd' eject: expanded name is `/dev/hdd' eject: `/dev/hdd' is not mounted eject: `/dev/hdd' is not a mount point eject: `/dev/hdd' is a multipartition device eject: trying to eject `/dev/hdd' using CD-ROM eject command eject: CD-ROM eject command succeeded # eject -vt /dev/hdd eject: device name is `/dev/hdd' eject: expanded name is `/dev/hdd' eject: `/dev/hdd' is not mounted eject: `/dev/hdd' is not a mount point eject: closing tray eject: CD-ROM tray close command failed: Input/output error /*EXAMPLE*/ /*HDPARM INFO*/ # hdparm -I /dev/hdd /dev/hdd: ATAPI CD-ROM, with removable media Model Number: TOSHIBA CD-ROM XM-6102B Serial Number: 4520304818 Firmware Revision: 1106 Standards: Used: ATAPI for CD-ROMs, SFF-8020i, r2.5 Supported: CD-ROM ATAPI-2 Configuration: DRQ response: 50us. Packet size: 12 bytes Capabilities: Cmd overlap, LBA, IORDY(cannot be disabled) Buffer size: 256.0kB DMA: sdma0 sdma1 sdma2 mdma0 mdma1 *mdma2 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 Cycle time: no flow control=120ns IORDY flow control=120ns /*HDPARM INFO*/ /*DRIVE INFO*/ #cat /proc/sys/dev/cdrom/info CD-ROM information, Id: cdrom.c 3.20 2003/12/17 drive name: hdd drive speed: 24 drive # of slots: 1 Can close tray: 1 Can open tray: 1 Can lock tray: 1 Can change speed: 1 Can select disk: 0 Can read multisession: 1 Can read MCN: 1 Reports media changed: 1 Can play audio: 1 Can write CD-R: 0 Can write CD-RW: 0 Can read DVD: 0 Can write DVD-R: 0 Can write DVD-RAM: 0 Can read MRW: 0 Can write MRW: 0 Can write RAM: 0 /*DRIVE INFO*/ Reproducible: Always Steps to Reproduce: 1.eject -v /dev/hdd (previously umounted OR empty tray, if eject has to unmount it will work, unless empty tray) 2.eject -vt /dev/hdd 3. Actual Results: eject: device name is `/dev/hdd' eject: expanded name is `/dev/hdd' eject: `/dev/hdd' is not mounted eject: `/dev/hdd' is not a mount point eject: closing tray eject: CD-ROM tray close command failed: Input/output error Also the cd light stayed on, and it would not mount, even if I tried to mount manually. Expected Results: It should have been able to mount as it does with other cd drives, or when it is "eject /dev/hdd" from a mounted drive and "eject -t /dev/hdd" with a cd in the drive.
I've seen lots of older drives that claim to be capable of open/close, but fail to work completely. In some cases it's been hardware manufactering defect (reproducable across multiple OS [BSD,Linux,Windows]), even on a 'new' drive. But in others it's just been a precursor to the hardware failing. Mind trying the toshibia drive in some other operating systems to see how reproducable it is?
It turns out it doesn't work with windows xp at all.
sounds like it's just too old a drive :/
