cd/dvd/bluray drive tray cannot be closed solved

[Member dirkd]

Helpful

Up

0

::

This doesn’t look very promising. I recognize the udevil error messages about ignored options from fstab, and the mount error messages about the missing mount point, but I never saw anything about reading the superblock. I never experimented with audio-CD’s yet, only data-CD’s and DVD’s.

The main problem is the continuously spitting out of a new disk, the first mount operation succeeds succesfully most of the time. The fact you don’t have that problem would seem to indicate that it’s due to a rare combination of hard- and software… I had hoped that every USB CD/DVD drive would behave in the same way. I would like to try another brand/model at home here, but I don’t see where I could find one right away, short of buying a new one, which is rather expensive if you also want BluRay capability.

[Member ModdIt]

Helpful

Up

0

::

Big differences in drive controller software and built in limitations. You wrote you are wanting to rip CD DVD. Many Blue ray and
some DVD writers will refuse to work for that, probable/pretty certain is some kind of industry copyright material blocker incorporation.
Blue Ray is a content industry patent, Sony CBS if I remember correctly.. Would not expect too much other than trouble

My prize possession is an early as new Lite on device, it will read most anything. I binned two asus devices, neither was old,
had read issues, inside built like a hongkong toy. I wanted to use the lasers for marking some layouts on wood, just not worth it.
reserve is Plex Store, also excellent. If you are lucky you can find drives like that in older desktop devices cheap or free, most
were rarely used.

[Member stevesr0]

Helpful

Up

0

::

Hi dirkd,

Unclear whether your goal is to use your bluray dvd/cd device with antix-21 or to use it specifically with zzzfm. If the former, why not substitute aother file manager.

I experienced a superblock error when trying to mount an audio cd, before checking and realizing that you don’t mount an audio cd, you just use a music player application and play it <g>. Not sure that this is relevant to the use of zzzfm causing the usb cd/dvd device to auto open.

stevesr0

[Member dirkd]

Helpful

Up

0

::

@stevesr0: I want, if at all possible, to stick to zzzFM. I have grown so fond of it over the years (in its SpaceFM incarnation), that I can’t imagine using anything else.

@Xecure: Isn’t there some hack I could use in the Devices>Settings menu of zzzFM? I’m thinking of the Autorun section there. You can enter some script lines that get executed on the event of Unmount, or Remove. Or maybe I could change something in the Device handlers or Protocol handlers section?

Something else I found out that may be meaningful to some more experiences user: I issued the command
udevil monitor
in a terminal, then ejected the mounted DVD in my portable drive by pressing the eject button on the device. I was greeted by the following message, that kept repeating without end, until I disconnected the drive from the USB ports:
changed: /org/freedesktop/UDisks/devices/sr1
(that was done on a second laptop with both a built-in sr0 and the portable sr1 drives). When I did the same thing with a disk in the built-in sr0, I got a similar message
changed: /org/freedesktop/UDisks/devices/sr0
but only repeated three times.

The fact that the message from sr1 keeps repeating is surely connected with the inability to change disks. Now does this shed any light on precisely what is going wrong here?

[Member ModdIt]

Helpful

Up

0

::

May I gently and politely remind you that xecure has already spent a lot of his free time to help you, at no charge.
Give him a break.

[Member Xecure]

Helpful

Up

0

::

dirkd wrote:

These are the lines in /etc/fstab pertaining to the CD drive (where ‘mount’ ignores the options from):

/dev/cdrom /media/cdrom iso9660 noauto,exec,user,ro 0 0
/dev/sr0 /media/sr0 iso9660 noauto,exec,user,ro 0 0

Change /dev/sr0 entry in fstab to:
/dev/sr0 /media/sr0 auto noauto,users,exec,ro 0 0
and create the /media/sr0 folder in case it doesn’t exist
sudo mkdir /media/sr0

And try again.

stevesr0 wrote:

I experienced a superblock error when trying to mount an audio cd, before checking and realizing that you don’t mount an audio cd, you just use a music player application and play it <g>. Not sure that this is relevant to the use of zzzfm causing the usb cd/dvd device to auto open.

It has been so long since I used a CD I no longer remember if the device could not be mounted. How did a person rip the audio files then, though a music player?

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member dirkd]

Helpful

Up

0

::

I found, well, not exactly the solution, but a workaround that I can live with. An UBUNTU user had exactly the same problem with a device very similar to mine. I will sketch his remedy in short below, in case another Antix user should need it. If you want to read the whole story you can find it here at the unix stackexchange forum. Let me add right away that, as a side-effect, the proposed cure disables the eject button on the drive, but you can still eject a disk through software, say in zzzFM. A small price to pay, if you ask me, for being able to switch disks freely.

Here’s how it goes. Locate the file ‘/lib/udev/rules.d/60-cdrom_id.rules’. To be on the safe side, make a backup copy of it. Then, with root permissions edit this text file. Search for the section

# media eject button pressed
ENV{DISK_EJECT_REQUEST}=="?*", RUN+="/usr/bin/eject $devnode", GOTO="cdrom_end"

and delete the ‘RUN+=…’ part in between the comma’s, so that it now reads

# media eject button pressed
ENV{DISK_EJECT_REQUEST}=="?*", GOTO="cdrom_end"

Save the edited file, and you’re done. This fix is not 100% permanent, in that certain upgrade operations on your OS could overwrite said file, an so undo the changes you made. These overwrites should be rare for most users however.

It would be nice if a truly expert user could pursue the matter further, to see what exactly is causing this endless loop of eject-commands that is apparently the cause of this problem, and why it only affects certain USB optical drives. And if a true solution that would not mess up the physical eject button could be found. It must be possible, since MX handles the matter flawlessly, as far as I can see.

For now I don’t mark this topic as [SOLVED] yet but, for me at least, it is not urgent anymore.

• This reply was modified 1 year, 5 months ago by dirkd.

[Member stevesr0]

Helpful

Up

0

::

Hi xecure,

I just did the following:

1) insert audio CD (John Pizzarelli and Daniel Jobim) in a usb attached LG slim portable DVD writer.
2) check in space FM file manager sr0 (audio) listed but no contents. When I click on sr0, I get an error message “udevil can’t determine the file type”.
3) Start VLC and select the audio cd and start it playing.
4) Enjoy the music in my headset.

About ripping – I have used abcde and it just works <g>.

Hi dirkd,

If you liked spaceFM, isn’t it still available in the repos for antiX-21? (I haven’t installed this yet – still running antiX-19 on this system. But I also have spaceFM on my Sid antiX install.)

stevesr0

• This reply was modified 1 year, 5 months ago by stevesr0.
• This reply was modified 1 year, 5 months ago by stevesr0.

[Member dirkd]

Helpful

Up

0

::

If I understood well what I read about it on the forum, SpaceFM is no longer actively supported. So it’s a dead end. zzzFM is a fork, and behaves (almost) identically to SpaceFM. So I’m quite happy really, and very grateful to Skidoo. Maintaining a file manager is surely a daunting task.

The problems I had with my CD-player would have been the same with SpaceFM, since they are actually udevil related.

[Member stevesr0]

Helpful

Up

0

::

hi dirkd,

I am running spaceFM on antiX19 and my usb connected slim DVD writer (non bluray) doesn’t have this problem.

Of course, it is reasonable to avoid using a no longer supported application if an equivalent (or better) supported one exists. But it would be interesting if spaceFM works in antiX-21 and DOESN’T show that problem.

stevesr0

[Member dirkd]

Helpful

Up

0

::

I admit I haven’t tried SpaceFM in combination with Antix21 yet, but I’m pretty sure it wouldn’t make any difference. The problem is probably connected with udevil, or some other deeper level process that is invoked by the filemanager, or for that part by just pressing the eject button on the device. So maybe I should change the title of this thread again (initially it didn’t mention zzzFM). Then again, maybe there is a way that zzzFM or SpaceFM could remedy the situation, given their extensive customizability.

For now I’ll pursue the 60-cdrom_id.rules lead just a little further, but if I can’t find any better solution, I can live with the situation as it is. I might try SpaceFM later, out of curiosity, but not if it conflicts with zzzFM.

[Member ModdIt]

Helpful

Up

0

::

The underlying problem has been around since at least 2008 https://bugzilla.redhat.com/show_bug.cgi?id=453095 and root cause is in the software of the CD DVD drive.
Some do not report that draw is in open or closed position. Device status returns CDS_NO_INFO for the CDROM_DRIVE_STATUS.
Countless drives may have the code in ROM.

All so called fixes are workarounds, have nothing at all to do with zzFM or the unmaintained SpaceFM it replaced. They are file managers.
Udevil is involved but not the root cause.

The rules method is one hotfix, Setting sysctl ‘dev.cdrom.autoclose’ to ‘0’ will probably still work.

Compare how another recent debian based distro with effective workaround is handling the issue, that may give good leads.

• This reply was modified 1 year, 5 months ago by ModdIt.
• This reply was modified 1 year, 5 months ago by ModdIt.

[Member dirkd]

Helpful

Up

0

::

After studying udevil and rules.d matter, and after pondering all kinds of complicated things I might try, I found the following simple solution to my problem. Admittedly with more luck then wisdom, as we say here. The solution doesn’t interfere with automatic mounting of optical disks, and the eject button on the CDROM device itself remains functional. I have verified that it doesn’t mess up built-in IDE or SATA connected optical drives in laptops. What I can’t test here at home is whether perhaps there are adverse effects with 5.25 inch built-in drives with motorized trays, although I don’t expect that to be the case. Maybe someone else could check this out?

Here’s how it goes. The procedure is largely the same (but better) then my previous solution.

Locate the file ‘/lib/udev/rules.d/60-cdrom_id.rules’. To be on the safe side, make a backup copy of it. Then, with root permissions edit this text file. Search for the section

# media eject button pressed
ENV{DISK_EJECT_REQUEST}=="?*", RUN+="/usr/bin/eject $devnode", GOTO="cdrom_end"

and just add the option ‘-T’ to the ‘eject’ command in the RUN+=… argument, so that it now reads

# media eject button pressed
ENV{DISK_EJECT_REQUEST}=="?*", RUN+="/usr/bin/eject -T $devnode", GOTO="cdrom_end"

Save the edited file, and you’re done. This fix is not 100% permanent, in that certain upgrade operations on your OS could overwrite said file, an so undo the changes you made. These overwrites should be rare for most users however. A better way to do it would be to make a copy of the 60-cdrom_id.rules file in the folder ‘/etc/udev/rules.d/’ and do the proposed edit on that copy. This copy should take precedence to the one in /lib/…, and, being part of /etc, should never be overwritten without at least a warning.

I will mark this thread as ‘solved’ now.

May I suggest that this small tweak could be brought to the attention of the Antix developers? If further tests don’t show any interference with the more standard types of optical drives, it could be incorporated in future updates, even if only a small number of users benefit from it.

[Member dirkd]

Helpful

Up

0

::

Seems I can’t mark the thread as ‘SOLVED’ myself. Moderator please? If you deem it necessary of course.

Btw: thank you all for comments and tests.

[Member seaken64]

Helpful

Up

0

::

I think the topic title is misleading in that it doesn’t have anything to do with zzzFM.

Seaken64

[Author]

Posts