The subject line says it all.

This just occurred out of the blue, no changes to settings or anything.

I found a thread from 2009 where Mythbuntu users found a bug that
(should) have fixed it:

http://svn.mythtv.org/trac/ticket/7212#comment:2

Some reported that it might be caused by mtd running as a daemon and
killing mtd from a terminal stops the behavior.


Didn't for me... "mtd:no process found"

Other thread I've found have the opposite problem, the tray refuses to
stay closed.


"eject -t" says:

eject: tried to use `/media/cdrom' as device name but it is no block device
eject: unable to find or open device for: `cdrom'




Any ideas?

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

> This just occurred out of the blue, no changes to settings or anything.

Can't say if it's the same in your situation, but I've seen several optical
drives fail in this way over the years. However, because I service office
PCs they were all running Windows.

So just saying - it might be the drive, and not the OS.


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On 09/27/2012 09:03 AM, compdoc wrote:



So just saying - it might be the drive, and not the OS.





Thanks compdoc!

You got me thinking and I realized I'd forgotten the first thing I
learned in networking classes... check the hardware first.
Turns out a different data cable made the difference and the drive is
behaving again.


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

>Turns out a different data cable made the difference and the drive is
behaving again.

Interesting. Was it a sata or an IDE cable?




--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On 09/27/2012 09:37 AM, CJ Tres wrote:

The subject line says it all.

This just occurred out of the blue, no changes to settings or anything.

I found a thread from 2009 where Mythbuntu users found a bug that
(should) have fixed it:
http://svn.mythtv.org/trac/ticket/7212#comment:2

Some reported that it might be caused by mtd running as a daemon and
killing mtd from a terminal stops the behavior.

Didn't for me... "mtd:no process found"

Other thread I've found have the opposite problem, the tray refuses to
stay closed.

"eject -t" says:

eject: tried to use `/media/cdrom' as device name but it is no block
device
eject: unable to find or open device for: `cdrom'


chances are that your CD/DVD is being referred to as /dev/cdrom1. I
think this occurs with an upgrade, where the existence of /dev/cdrom is
found so on this go around it is bumped up to /dev/cdrom1. I dimly
recall having to edit some obscure file to reset cdrom1 back to cdrom. I
think it was in hal or udev or something like that. Maddening, I know. Ric




--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On 09/27/2012 06:33 PM, compdoc wrote:

Turns out a different data cable made the difference and the drive is

behaving again.

Interesting. Was it a sata or an IDE cable?



It's sata III - I'm thinking the other was sata II.
Not sure if there's any way to differentiate them physically, other than
the newer one has clips and one end is 90 degrees they look the same.



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On 09/27/2012 07:23 PM, Ric Moore wrote:



chances are that your CD/DVD is being referred to as /dev/cdrom1. I
think this occurs with an upgrade, where the existence of /dev/cdrom is
found so on this go around it is bumped up to /dev/cdrom1. I dimly
recall having to edit some obscure file to reset cdrom1 back to cdrom. I
think it was in hal or udev or something like that. Maddening, I know. Ric





I never have done an upgrade, always a clean install.
Still that's a good point to remember.
Thanks


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users