[ltp] RE: Problem ejecting cdrom drive! T520

Mon, 20 Feb 2012 09:44:20 -0600

--=-xVAm8y/8D9TKSpDTznc5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

-------- Forwarded Message --------

> Message: 1
> Date: Sun, 19 Feb 2012 14:42:53 -0800
> From: keitho@strucktower.com
> To: linux-thinkpad@linux-thinkpad.org
> Subject: [ltp] Problem ejecting cdrom drive! T520
> Reply-To: linux-thinkpad@linux-thinkpad.org
> 
> Today I got to the point where I couldn't open my cdrom drive. Here's the
> output from eject -v:
> 
> eject: using default device `cdrom'
> eject: device name is `cdrom'
> eject: expanded name is `/dev/cdrom'
> eject: `/dev/cdrom' is a link to `/dev/sr0'
> eject: `/dev/sr0' is not mounted
> eject: `/dev/sr0' is not a mount point
> eject: `/dev/sr0' is not a multipartition device
> eject: trying to eject `/dev/sr0' using CD-ROM eject command
> eject: CD-ROM eject command failed
> eject: trying to eject `/dev/sr0' using SCSI commands
> eject: SCSI eject failed
> eject: trying to eject `/dev/sr0' using floppy eject command
> eject: floppy eject command failed
> eject: trying to eject `/dev/sr0' using tape offline command
> eject: tape offline command failed
> 
> I have a fairly new Lenovo Thinkpad T50, Debian with 3.0.0-1-amd64 kernel
> using i3wm.
> 
> I had been seeing some problem with programs not being able to eject, and
> I have had to resort to using "eject", but as you can see that is not
> working now. When it was working there were no signs of trouble- odd
> noises or such.
> 
> Can someone tell me what's going on here? AFAIK I haven't changed anythin=
> g
> recently that might cause this. I'm unfamiliar with how drives work so
> don't know where to start looking.
> 
> Thanks,
> Keith Ostertag

All I have is my experiences with my Thinkpad X220t and its Ultrabase
with an Ultra-bay DVD drive.  In order to automatically handle whichever
media to load into your CD/DVD drive,
the drive gets special handling. It is a similar dance to what happens
when you connect a USB drive or media stick only you are loading media
into a drive not actually connecting the drive itself.

The result is that unless there is mounted media in your CD/DVD drive,
the drive almost does not exist ... until the next media load.  The
X220t+Base+Bay has a "drive module" that will
eject in addition to the CD or DVD media.  Win-doze will happily process
the "drive eject"
separately from the "media eject".  No linux I've tried will accomplish
this.  You cannot
remove a drive with media mounted and once you unmount the media there
is no drive
to respond to the eject request ... but it works on win-doze.

I hope this shed a drop of light on what is going on. If you learn more,
please share.

Cheers,
~~~ 0;-Dan

--=-xVAm8y/8D9TKSpDTznc5
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
-------- Forwarded Message --------<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
Message: 1
Date: Sun, 19 Feb 2012 14:42:53 -0800
From: <A HREF="mailto:keitho@strucktower.com">keitho@strucktower.com</A>
To: <A HREF="mailto:linux-thinkpad@linux-thinkpad.org">linux-thinkpad@linux-thinkpad.org</A>
Subject: [ltp] Problem ejecting cdrom drive! T520
Reply-To: <A HREF="mailto:linux-thinkpad@linux-thinkpad.org">linux-thinkpad@linux-thinkpad.org</A>

Today I got to the point where I couldn't open my cdrom drive. Here's the
output from eject -v:

eject: using default device `cdrom'
eject: device name is `cdrom'
eject: expanded name is `/dev/cdrom'
eject: `/dev/cdrom' is a link to `/dev/sr0'
eject: `/dev/sr0' is not mounted
eject: `/dev/sr0' is not a mount point
eject: `/dev/sr0' is not a multipartition device
eject: trying to eject `/dev/sr0' using CD-ROM eject command
eject: CD-ROM eject command failed
eject: trying to eject `/dev/sr0' using SCSI commands
eject: SCSI eject failed
eject: trying to eject `/dev/sr0' using floppy eject command
eject: floppy eject command failed
eject: trying to eject `/dev/sr0' using tape offline command
eject: tape offline command failed

I have a fairly new Lenovo Thinkpad T50, Debian with 3.0.0-1-amd64 kernel
using i3wm.

I had been seeing some problem with programs not being able to eject, and
I have had to resort to using &quot;eject&quot;, but as you can see that is not
working now. When it was working there were no signs of trouble- odd
noises or such.

Can someone tell me what's going on here? AFAIK I haven't changed anythin=
g
recently that might cause this. I'm unfamiliar with how drives work so
don't know where to start looking.

Thanks,
Keith Ostertag
</PRE>
</BLOCKQUOTE>
 
All I have is my experiences with my Thinkpad X220t and its Ultrabase with an Ultra-bay DVD drive.&nbsp; In order to automatically handle whichever media to load into your CD/DVD drive, 
the drive gets special handling. It is a similar dance to what happens when you connect a USB drive or media stick only you are loading media into a drive not actually connecting the drive itself. 
 
The result is that unless there is mounted media in your CD/DVD drive, the drive almost does not exist ... until the next media load.&nbsp; The X220t+Base+Bay has a &quot;drive module&quot; that will 
eject in addition to the CD or DVD media.&nbsp; Win-doze will happily process the &quot;drive eject&quot; 
separately from the &quot;media eject&quot;.&nbsp; No linux I've tried will accomplish this.&nbsp; You cannot 
remove a drive with media mounted and once you unmount the media there is no drive 
to respond to the eject request ... but it works on win-doze. 
 
I hope this shed a drop of light on what is going on. If you learn more, please share. 
 
Cheers, 
~~~ 0;-Dan 
 
</BODY>
</HTML>

--=-xVAm8y/8D9TKSpDTznc5--