failure to open empty cd/dvd drive

On 4/15/08, siafok <email address hidden> wrote:
>
> Public bug reported:
>
> Hello, I'm on Hardy Heron 2.6.24-16-generic, my computer is i686
> libexo 0.3.4-3ubuntu4
> Little different situation than in #195649
> When my dvd drive is empty and closed command: 'exo-eject -ed /dev/sr0'
> does nothing except message (in window, not in terminal): 'Failed to eject
> "/dev/sr0". Device "/dev/sr0" not found in file system device table'.
> When i do: 'gnome-eject -ed /dev/sr0' or 'eject /dev/sr0' dvd tray opens.
> xfce4-cddrive-plugin does not open empty tray too, without any message,
> even when I built it with debug.
>
> ** Affects: exo (Ubuntu)
> Importance: Undecided
> Status: New

Correct me if I'm wrong, but might this be because Xubuntu is using
gnome-mount right now instead of exo?

Thank you for an answer but there is few (maybe more) things I dont understand. Even if you are right and Xubuntu uses gnome-mount this doesnt explain why exo doesnt work on Hardy when it works on Gutsy. And why xfce4-cddrive-plugin doesnt work on Hardy when it works on Gutsy.

I dont think you are right because Thunar (and xfce4-cddrive-plugin) has libexo dependency but no gnome-mount dependency either in Gutsy and Hardy.

exo doesnt work for me only in one situation explained by me in bug description

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? I attempted to confirm this, but my drive ejects if a there is a cd in it and I use exo-eject -ed /dev/scd0. Thanks in advance.

Hi, thank you for attention.

My drive doesn't eject if tray is e m p t y as I said above.
'exo-eject -ed /dev/scd0' still gives me 'Failed to eject "/dev/sr0". Device "/dev/sr0" not found in file system device table' (in gtk window).
But now I suppose this is not a bug in exo because 'gnome-eject /dev/scd0' gives me nothing - cd drive does not open and no error prompts.
Maybe this is my hal daemon problem because 'eject /dev/scd0' works fine. 'eject' does not use hal, does it?

Thanks for reporting this bug and any supporting documentation.
I can confirm that this bug exists on Hardy Heron, Version 8.04.01 with libexo-0.3.4-3ubuntu4 installed.
Since this package is installed by default installation, exo-eject should be expected to open the drawer of the cd/dvd drive when issued in terminal. This command does work if a cd is in the drive when issued.
If the command exo-eject is given with no cd in the drive, the command fails and gives an error "Failed to eject /dev/???" "Device /dev/??? not found in the file system table".
If the command gnome-eject is given, the command fails and gives no error messages. This is a new failure under 8.04.01, as stated by the original reporter in the 2008-07-18 followup.
Expectations with both commands are:
 the drive should be recognized as valid if in /dev
 the drive should eject the drawer/tray whether or not a cd is in
 this should continue to work between versions

This is reproducable at any time by issueing the commands in a terminal window

Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Attempting this in the latest development version, Jaunty Jackalope (9.04) up to date as of 2009-02-12, it still fails to eject the tray if there is no cd in the drive. If a cd is in the drive, "exo-eject -ed /dev/sr0" in a terminal ejects the disc by opening the tray.

With no disc in the drive, I receive an error message 'Failed to eject "/dev/sr0. Device "/dev/sr0" not found in file system device table.' If the device is not found, it should not be found with the cd in it, should it?

Just came to this bug when sorting out my "optical collection". Has this something to do if you have two optical drives?
In 9.10 I cannot eject a drive when it has just read a faulty CD/DVD and it cannot eject an empty writeable, so I need to do "eject /dev/cdrom", "eject /dev/cdrw0" or something like that. Even that doesn't help all the time.

This is in my log when trying to eject (or when it tries to read the DVD in it):
Sep 27 13:45:24 truus-desktop kernel: [11876.503399] sr 5:0:1:0: [sr1] Add. Sense: Logical block address out of range
Sep 27 13:45:24 truus-desktop kernel: [11876.508247] sr 5:0:1:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 27 13:45:24 truus-desktop kernel: [11876.508259] sr 5:0:1:0: [sr1] Sense Key : Illegal Request [current]
Sep 27 13:45:24 truus-desktop kernel: [11876.508269] sr 5:0:1:0: [sr1] Add. Sense: Logical block address out of range
Sep 27 13:45:24 truus-desktop kernel: [12018.105026] sr 5:0:1:0: [sr1] Unhandled sense code
Sep 27 13:45:33 truus-desktop kernel: [12018.105033] sr 5:0:1:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 27 13:45:33 truus-desktop kernel: [12018.105039] sr 5:0:1:0: [sr1] Sense Key : Medium Error [current]
Sep 27 13:45:33 truus-desktop kernel: [12018.105046] sr 5:0:1:0: [sr1] Add. Sense: No seek complete
Sep 27 13:45:33 truus-desktop kernel: [12018.105062] __ratelimit: 66 callbacks suppressed
Sep 27 13:45:33 truus-desktop kernel: [12026.683703] sr 5:0:1:0: [sr1] Unhandled sense code

and this in my syslog:
Sep 27 13:46:23 truus-desktop kernel: [12068.267101] sr 5:0:1:0: [sr1] Unhandled sense code
Sep 27 13:46:23 truus-desktop kernel: [12068.267107] sr 5:0:1:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 27 13:46:23 truus-desktop kernel: [12068.267113] sr 5:0:1:0: [sr1] Sense Key : Medium Error [current]
Sep 27 13:46:23 truus-desktop kernel: [12068.267120] sr 5:0:1:0: [sr1] Add. Sense: No seek complete
Sep 27 13:46:23 truus-desktop kernel: [12068.267127] end_request: I/O error, dev sr1, sector 0
Sep 27 13:46:23 truus-desktop kernel: [12068.267136] Buffer I/O error on device sr1, logical block 0
Sep 27 13:46:23 truus-desktop kernel: [12068.267142] Buffer I/O error on device sr1, logical block 1
Sep 27 13:46:23 truus-desktop kernel: [12076.970420] sr 5:0:1:0: [sr1] Unhandled sense code
Sep 27 13:46:35 truus-desktop kernel: [12076.970427] sr 5:0:1:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 27 13:46:35 truus-desktop kernel: [12076.970433] sr 5:0:1:0: [sr1] Sense Key : Medium Error [current]
Sep 27 13:46:35 truus-desktop kernel: [12076.970441] sr 5:0:1:0: [sr1] Add. Sense: No seek complete
Sep 27 13:46:35 truus-desktop kernel: [12076.970448] end_request: I/O error, dev sr1, sector 0
Sep 27 13:46:35 truus-desktop kernel: [12076.970456] Buffer I/O error on device sr1, logical block 0
Sep 27 13:46:35 truus-desktop kernel: [12076.970462] Buffer I/O error on device sr1, logical block 1
Sep 27 13:46:35 truus-desktop kernel: [12089.297855] sr 5:0:1:0: [sr1] Unhandled sense code

I can say if Ubuntu works on this pc, then it will probably work on any pc... The error was not existent in 9.04. More problematic (but don't know if this has s...

In natty, the mount/eject code has been dropped from exo 0.5.5, and is now handled directly by the "new" thunar (it will be uploaded after the alpha1 is released) and gio/gvfs. Reaffecting.

Exo-eject was removed in natty, and it should work fine using thunar & gio.