Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

No cdrom device

82 views
Skip to first unread message

Ed Jabbour

unread,
Dec 23, 2011, 12:40:01 PM12/23/11
to
CDROM tray will not respond to "eject":
========================
[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block device
eject: tried to use `/dev/scd0' as device name but it is no block device
eject: unable to find or open device for: `cdrom'
=========================

Perhaps related, dmesg reveals:
==============================
6.720030] ata1: link is slow to respond, please be patient (ready=0)
[ 11.704028] ata1: device not ready (errno=-16), forcing hardreset
[ 16.900028] ata1: link is slow to respond, please be patient (ready=0)
[ 21.716029] ata1: SRST failed (errno=-16)
[ 26.912027] ata1: link is slow to respond, please be patient (ready=0)
[ 31.728027] ata1: SRST failed (errno=-16)
[ 36.924030] ata1: link is slow to respond, please be patient (ready=0)
[ 66.772029] ata1: SRST failed (errno=-16)
[ 71.800028] ata1: SRST failed (errno=-16)
[ 71.811047] ata1: reset failed, giving up
[ 71.811185] ata2: port disabled--ignoring
=============================

modprobe cdrom sr_mod:
==============================
FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686-
pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown
parameter (see dmesg)

728.919036] cdrom: Unknown parameter `sr_mod'
===================================

Nor will the tray open manually, except that it does if on reboot, I push the
button before GRUB takes over. Running testing with the 3.1.0-1-686-pae
kernel, although the problem persists no matter which kernel I boot into.

Any advice, pointers, etc. appreciated.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20111223121...@att.net

Raf Czlonka

unread,
Dec 23, 2011, 12:50:02 PM12/23/11
to
On Fri, Dec 23, 2011 at 05:18:47PM GMT, Ed Jabbour wrote:
> CDROM tray will not respond to "eject":
> ========================
> [Fri Dec 23] edj:~$ eject
> eject: tried to use `/media/cdrom0' as device name but it is no block device
> eject: tried to use `/dev/scd0' as device name but it is no block device
> eject: unable to find or open device for: `cdrom'
> =========================

Which device is you optical drive?

> Perhaps related, dmesg reveals:
> ==============================
> 6.720030] ata1: link is slow to respond, please be patient (ready=0)
> [ 11.704028] ata1: device not ready (errno=-16), forcing hardreset
> [ 16.900028] ata1: link is slow to respond, please be patient (ready=0)
> [ 21.716029] ata1: SRST failed (errno=-16)
> [ 26.912027] ata1: link is slow to respond, please be patient (ready=0)
> [ 31.728027] ata1: SRST failed (errno=-16)
> [ 36.924030] ata1: link is slow to respond, please be patient (ready=0)
> [ 66.772029] ata1: SRST failed (errno=-16)
> [ 71.800028] ata1: SRST failed (errno=-16)
> [ 71.811047] ata1: reset failed, giving up
> [ 71.811185] ata2: port disabled--ignoring
> =============================

Might be related, see below.

> modprobe cdrom sr_mod:
> ==============================
> FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686-
> pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown
> parameter (see dmesg)

You're trying to load two modules (cdrom and sr_mod) and modprobe treats
the second one as a parameter to the first one.
You should load modules one by one.

> 728.919036] cdrom: Unknown parameter `sr_mod'

Which part of the above message is not clear? ;^)

> Nor will the tray open manually, except that it does if on reboot, I push the
> button before GRUB takes over. Running testing with the 3.1.0-1-686-pae
> kernel, although the problem persists no matter which kernel I boot into.
>
> Any advice, pointers, etc. appreciated.

The above dmesg messages might point to faulty drive or cable.
Does the optical drive work at all, e.g. under another OS?

Regards,
--
Raf


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20111223174...@linuxstuff.pl

Wayne Topa

unread,
Dec 23, 2011, 3:40:02 PM12/23/11
to
Locate your cdrom with:

$dmesg |grep -A2 B2 cdrom

Which in my case returns;

~$ dmesg |grep -A2 -B2 cdrom
[ 2.592157] sd 2:0:0:0: [sda] Attached SCSI disk
[ 2.640560] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw
xa/form2 cdda tray
[ 2.640634] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.640848] sr 0:0:0:0: Attached scsi CD-ROM sr0
[ 2.704036] usb 4-1: new full speed USB device number 2 using ohci_hcd

Which shows my cdrom is /dev/sd0

I eject with:
eject /dev/sr0

or with this line in my /etc/fstab
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

eject /media/cdrom0

HTH

WT



>
>


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/4EF4E6...@gmail.com

Wayne Topa

unread,
Dec 23, 2011, 6:40:01 PM12/23/11
to
Woops ^^^ /dev/sr0 sorry
>
> I eject with:
> eject /dev/sr0
>
> or with this line in my /etc/fstab
> /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
>
> eject /media/cdrom0
>
> HTH
>
> WT
>
>
>
>>
>>
>


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/4EF50F11...@gmail.com

Vincent Lefevre

unread,
Dec 23, 2011, 7:40:02 PM12/23/11
to
On 2011-12-23 18:30:25 -0500, Wayne Topa wrote:
> On 12/23/2011 03:38 PM, Wayne Topa wrote:
> >On 12/23/2011 12:18 PM, Ed Jabbour wrote:
> >>CDROM tray will not respond to "eject":
> >>========================
> >>[Fri Dec 23] edj:~$ eject
> >>eject: tried to use `/media/cdrom0' as device name but it is no block
> >>device
> >>eject: tried to use `/dev/scd0' as device name but it is no block device
> >>eject: unable to find or open device for: `cdrom'
> >>=========================

Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).

> >~$ dmesg |grep -A2 -B2 cdrom
> >[ 2.592157] sd 2:0:0:0: [sda] Attached SCSI disk
> >[ 2.640560] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2
> >cdda tray
> >[ 2.640634] cdrom: Uniform CD-ROM driver Revision: 3.20
> >[ 2.640848] sr 0:0:0:0: Attached scsi CD-ROM sr0
> >[ 2.704036] usb 4-1: new full speed USB device number 2 using ohci_hcd
> >
> >Which shows my cdrom is /dev/sd0
>
> Woops ^^^ /dev/sr0 sorry
> >
> >I eject with:
> >eject /dev/sr0
> >
> >or with this line in my /etc/fstab
> >/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
> >
> >eject /media/cdrom0

Running lshw *as root* says which /dev files can be used.
In my case:

*-cdrom
description: DVD-RAM writer
product: DVD+-RW TS-U633A
vendor: TSSTcorp
physical id: 1
bus info: scsi@1:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/dvd
logical name: /dev/dvdrw
logical name: /dev/sr0
version: D300
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc

I've chosen to use /dev/cdrom in case /dev/sr0 would be replaced
by something else.

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20111224003...@xvii.vinc17.org

Ed Jabbour

unread,
Dec 23, 2011, 8:40:01 PM12/23/11
to
On Friday, December 23, 2011 7:32:22 PM Vincent Lefevre wrote:

>Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).

Why do I still get error msgs referring to scd0??

> Running lshw *as root* says which /dev files can be used.
> In my case:
>
> *-cdrom
> description: DVD-RAM writer
> product: DVD+-RW TS-U633A
> vendor: TSSTcorp
> physical id: 1
> bus info: scsi@1:0.0.0
> logical name: /dev/cdrom
> logical name: /dev/cdrw
> logical name: /dev/dvd
> logical name: /dev/dvdrw
> logical name: /dev/sr0
> version: D300
> capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
> configuration: ansiversion=5 status=nodisc
>
> I've chosen to use /dev/cdrom in case /dev/sr0 would be replaced
> by something else.

lshw output in my case has no *cdrom entry at all. I rebooted, opened the
tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom
drive. No luck - booted from the hard drive.

Also, modprobe sr_mod gave me sg0 in /dev (?). mount /dev/sg0
/mnt/cdrom gave mount: /dev/sg0 is not a block device

This is getting wierder and wierder.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20111223201...@att.net

Vincent Lefevre

unread,
Dec 24, 2011, 6:50:02 AM12/24/11
to
On 2011-12-23 20:14:32 -0500, Ed Jabbour wrote:
> On Friday, December 23, 2011 7:32:22 PM Vincent Lefevre wrote:
> >Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).
>
> Why do I still get error msgs referring to scd0??

Perhaps because it is mentioned in /etc/fstab?

> > Running lshw *as root* says which /dev files can be used.
> > In my case:
> >
> > *-cdrom
> > description: DVD-RAM writer
> > product: DVD+-RW TS-U633A
> > vendor: TSSTcorp
> > physical id: 1
> > bus info: scsi@1:0.0.0
> > logical name: /dev/cdrom
> > logical name: /dev/cdrw
> > logical name: /dev/dvd
> > logical name: /dev/dvdrw
> > logical name: /dev/sr0
> > version: D300
> > capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
> > configuration: ansiversion=5 status=nodisc
> >
> > I've chosen to use /dev/cdrom in case /dev/sr0 would be replaced
> > by something else.
>
> lshw output in my case has no *cdrom entry at all.

Note: I recall that lshw must be run as root (if I run lshw as a
normal user, I don't get a *-cdrom entry either). Otherwise perhaps
your drive is not recognized.

> I rebooted, opened the tray manually, inserted a Knoppix disk and
> set the BIOS to boot off the cdrom drive. No luck - booted from the
> hard drive.
>
> Also, modprobe sr_mod gave me sg0 in /dev (?). mount /dev/sg0
> /mnt/cdrom gave mount: /dev/sg0 is not a block device
>
> This is getting wierder and wierder.

Here I don't need "modprobe sr_mod". It is loaded automatically.

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20111224114...@xvii.vinc17.org

Hugo Vanwoerkom

unread,
Dec 24, 2011, 11:00:02 AM12/24/11
to
On 12/23/2011 06:32 PM, Vincent Lefevre wrote:
> On 2011-12-23 18:30:25 -0500, Wayne Topa wrote:
>> On 12/23/2011 03:38 PM, Wayne Topa wrote:
>>> On 12/23/2011 12:18 PM, Ed Jabbour wrote:
>>>> CDROM tray will not respond to "eject":
>>>> ========================
>>>> [Fri Dec 23] edj:~$ eject
>>>> eject: tried to use `/media/cdrom0' as device name but it is no block
>>>> device
>>>> eject: tried to use `/dev/scd0' as device name but it is no block device
>>>> eject: unable to find or open device for: `cdrom'
>>>> =========================
>
> Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).
>

I believe that was after a udev update. It showed up in the changelog.

Hugo


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/jd4srj$h58$1...@dough.gmane.org

Vincent Lefevre

unread,
Dec 24, 2011, 11:40:01 AM12/24/11
to
On 2011-12-24 09:58:43 -0600, Hugo Vanwoerkom wrote:
> On 12/23/2011 06:32 PM, Vincent Lefevre wrote:
> >Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).
>
> I believe that was after a udev update. It showed up in the changelog.

Indeed:

udev (175-1) unstable; urgency=low
[...]
* 50-udev-default.rules: removed the obsolete scd%n symlinks.
[...]
-- Marco d'Itri <m...@linux.it> Fri, 18 Nov 2011 03:05:39 +0100

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2011122416...@xvii.vinc17.org

Bill Marcum

unread,
Dec 29, 2011, 3:20:01 AM12/29/11
to
In gmane.linux.debian.user, you wrote:
>
> lshw output in my case has no *cdrom entry at all. I rebooted, opened the
> tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom
> drive. No luck - booted from the hard drive.
>
That sounds like a hardware problem with the cdrom drive.

> Also, modprobe sr_mod gave me sg0 in /dev (?). mount /dev/sg0
> /mnt/cdrom gave mount: /dev/sg0 is not a block device
>
> This is getting wierder and wierder.
>
>


--
"Never believe the attribution of a quotation you find on the Internet."
(George Bernard Shaw)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/E1Rg7jv-...@lat.local

edj...@gmail.com

unread,
Dec 29, 2011, 11:20:01 AM12/29/11
to
On Wednesday, December 28, 2011 11:37:15 PM Bill Marcum wrote:
> In gmane.linux.debian.user, you wrote:
> > lshw output in my case has no *cdrom entry at all. I rebooted, opened
> > the tray manually, inserted a Knoppix disk and set the BIOS to boot off
> > the cdrom drive. No luck - booted from the hard drive.
>
> That sounds like a hardware problem with the cdrom drive.

No, it wasn't a hardware problem. After much travail with udev, modprobe,
interrupts, etc. and leariing more about dmesg output than I care to know, I
thought - well, no sr0? Then make one!

touch /dev/sr0
chown root:disk /dev/sr0
chmod 660 /dev/sr0

And that was that. Sometimes the simplest, most obvious solution is the one
that eludes us the most.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/201112291110...@gmail.com

Vincent Lefevre

unread,
Dec 29, 2011, 11:50:03 AM12/29/11
to
On 2011-12-29 11:10:52 -0500, edj...@gmail.com wrote:
> On Wednesday, December 28, 2011 11:37:15 PM Bill Marcum wrote:
> > In gmane.linux.debian.user, you wrote:
> > > lshw output in my case has no *cdrom entry at all. I rebooted, opened
> > > the tray manually, inserted a Knoppix disk and set the BIOS to boot off
> > > the cdrom drive. No luck - booted from the hard drive.
> >
> > That sounds like a hardware problem with the cdrom drive.
>
> No, it wasn't a hardware problem. After much travail with udev, modprobe,
> interrupts, etc. and leariing more about dmesg output than I care to know, I
> thought - well, no sr0? Then make one!
>
> touch /dev/sr0
> chown root:disk /dev/sr0
> chmod 660 /dev/sr0

You shouldn't need to do that manually. There's something broken
on your system.

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2011122916...@xvii.vinc17.org

edj...@gmail.com

unread,
Dec 29, 2011, 1:10:02 PM12/29/11
to
On Thursday, December 29, 2011 11:39:45 AM Vincent Lefevre wrote:
> >
> > No, it wasn't a hardware problem. After much travail with udev,
> > modprobe, interrupts, etc. and leariing more about dmesg output than I
> > care to know, I thought - well, no sr0? Then make one!
> >
> > touch /dev/sr0
> > chown root:disk /dev/sr0
> > chmod 660 /dev/sr0
>
> You shouldn't need to do that manually. There's something broken
> on your system.

Perhaps, but the device survives reboots, so -- if all is well, then it is.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/201112291301...@gmail.com

Charlie

unread,
Dec 29, 2011, 3:50:02 PM12/29/11
to
On Thu, 29 Dec 2011 13:01:54 -0500 "edj...@gmail.com edj...@gmail.com"
suggested this:

>On Thursday, December 29, 2011 11:39:45 AM Vincent Lefevre wrote:
>> >
>> > No, it wasn't a hardware problem. After much travail with udev,
>> > modprobe, interrupts, etc. and leariing more about dmesg output
>> > than I care to know, I thought - well, no sr0? Then make one!
>> >
>> > touch /dev/sr0
>> > chown root:disk /dev/sr0
>> > chmod 660 /dev/sr0
>>
>> You shouldn't need to do that manually. There's something broken
>> on your system.
>
>Perhaps, but the device survives reboots, so -- if all is well, then
>it is.

After an upgrade a couple of weeks ago, had to change the
cdrom's from /dev/scd* to /dev/sr*

Have no idea why? However, leaving them as /dev/scd* they weren't
recognised.

Charlie
--
----------------------------------------
Registered Linux User:- 329524
***********************************************

In prosperity our friends know us; in adversity we know our friends.
---- Churton Collins

***********************************************
Debian GNU/Linux - just the best way to create magic
_______________________________________________


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20111230075308.06233acd@taowild
0 new messages