Can't Eject Disc After unmount?

schorschi · #1 13th July 2012, 04:36 AM

In Fedora 17... Can't Eject Disc After unmount?

Sequence...

Insert cdrom disc
Mount it

# mkdir -p /media/dvdrom
# mount /dev/cdrom /media/dvdrom

<Do something, Copy Files, Whatever...>

Unmount it

# umount /media/dvdrom

Press Eject Button, Nothing Happens?
What now? Kind of weird issue, someone has to have experienced this?

SlowJet · #2 13th July 2012, 05:32 AM

I just tried a dvd and this is what happened.

dvd inserted, a popup asked me how to open it. I selected open folder.
dvd mount and opened contents in file manager.

I right on dvd name in file manager left tree, then clicked on eject.
It took about 10 seconds then ejected.

So, it looks like you don't need to umount or mount.
The question is what makes that happen?
I thoht it wa autofs, but I do not have the installed?

SJ

rajhat · #3 13th July 2012, 06:48 AM

# eject
#eject /dev/sr0

SlowJet · #4 13th July 2012, 11:01 AM

Quote:

Originally Posted by rajhat

# eject
#eject /dev/sr0

I wish everything was like that,
a package, a command, and a menu item.

SJ

devart · #5 1st September 2012, 08:58 PM

THANK YOU!

I wish i had a fountain of knowledge to drink from all day long, thanks rajhat

StephenH · #6 2nd September 2012, 03:32 AM

Here's a corollary question: Why does it seem like the CD drive (hooked to a PATA connection) stops working after doing something and then ejecting it. After closing it, it is unresponsive. Neither an eject /dev/sr1 nor a button press on the physical button will get it to respond. It is like the system forgets that it is there, even though it shows up in the list of drives in palimpsest.

george_toolan · #7 2nd September 2012, 10:59 AM

How many drives do you have?

The first one is usually called /dev/sr0

Does this problem only happen with Linux?

What happens when you switch on your computer and then insert a Fedora LiveCD and try to start from that one?

An old pata drive may be broken by now or the disc is unreadable ;-)

StephenH · #8 3rd September 2012, 03:49 AM

Quote:

Originally Posted by george_toolan

How many drives do you have?

The first one is usually called /dev/sr0

Does this problem only happen with Linux?

What happens when you switch on your computer and then insert a Fedora LiveCD and try to start from that one?

An old pata drive may be broken by now or the disc is unreadable ;-)

Two drives. The first is connected via SATA. The second is the PATA drive, connected to the primary master connection.

The SATA drive is /dev/sr0
The PATA drive is /dev/sr1

I'm not sure. I only rarely (about once in a blue moon) boot into the other OS, and I have not tried copying a disk there (putting original in /dev/sr0 and blank in /dev/sr1). I can't say whether it would happen under the other OS.

After reconfiguring the BIOS to swap the order of the two drives, I proceeded to boot a live F17 LXDE i686 spin. It did not seem to have any problems doing so. I only tested briefly, and since I was running on a live CD, I could not test whether the same problem would occur there.

The drive does not seem to be broken, and the disk was not unreadable. This seems to happen after I complete an operation. If I shut the CD drawer, that is when it becomes unresponsive. However, immediately previous operation did complete successfully.

Maryyy · #9 3rd September 2012, 06:46 PM

This was happening to me before too and it still does. I had a thread about it somewhere here.
Basically, it happens only with the PATA drive, the other SATA one isn't affected.

Symptoms.
Insert medium, let it mount. Eject it. Now upon manual closing of the tray, it will not react on manual open anymore till next reboot.

eject /dev/sr0 has no effect.

Systemd, Gnome3 s4!t!, GRUB2, fuEFI and impossible to eject drive. This OS is not what I used 2 years before.

Om Namo Kernel Vasudevaya...

StephenH · #10 3rd September 2012, 11:54 PM

Unfortunately, I have to agree with you. Things used to be predictable, reliable, and rock solid. The changes that have come recently which manifest themselves in things like this are evidence that some of these changes were not quite ready for prime time. It complicates my ability to try to convince people that there are valid alternatives to the dominant OS.

I don't blame it on GRUB2. It seems to be okay. However, the elimination of HAL is likely where this originates. Time to check bugzilla to see if it has already been reported. If not, then it is time to do so.

--------------------

Edit: I filed a bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=854074