Cdrom drive not recognized automatically

Please use ubuntu-bug when filing bugs. There is no debugging information at all here.

Which udev version are you running? Yesterday I did two udev uploads (now 151-10) which should fix a lot of these problems.

Please make sure you are running -10, check if it is still happening, and if so, please do "apport-collect 562092". Thanks!

i am running udev version is 151-10.

This bug affects me also. I can collect the data, but it probably won't let me submit info to this bug - should I open a new one and run apport-collect against it?

The CD-ROM drive closes after a few seconds if I open it, and if I do manage to insert a 2nd CD it doesn't mount - I can't even mount it using sudo commands. There is no /dev/cdrom to mount.

Ignore my last comment - it seems to be working now.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

i am on lucid 64bit and i m running udev 151-10

Can you please install udev 151-10pitti2 from my PPA and see how it goes? Thanks!

  sudo add-apt-repository ppa:pitti/ppa
  sudo apt-get update
  sudo apt-get install udev

I installed 3 packages udev and 2 libraries packages for udev.

In first time, DVD recognized automatically an mounted on desktop and in shortcuts list after cd appear only in shortcuts list

 if i use eject button on disc drive :
- dvd icon stay on desktop and in shortcuts list
- cd tray opened but closed automatically.

 if i use eject command
- cd tray opened but closed automatically.

Sorry i tried to explain more clearly

DVD recognized automatically and mounted on desktop and appear in shortcuts list.
If i eject DVD, cd tray close automatically and DVD not mounted but appear in shortcuts list.

same bug with udev 151-11

  sudo add-apt-repository ppa:pitti/ppa
  sudo apt-get update
  sudo apt-get install udev

worked for me, thank you so much Mr. Pitt!

sorry spoke to soon, drive doesn't automatically close anymore, but still doesn't mount blank dvd

forgot to mention burner is HL-DT-ST' 'DVDRAM GH41N running lucid beta 2 udev 151-11

Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
MachineType: eMachines eMachines E510
Package: udev 151-12
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=1303c4ed-abd1-4cff-bfcf-042985699776 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/11/2008
dmi.bios.vendor: EMACHINES
dmi.bios.version: V1.42
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Rhine
dmi.board.vendor: EMACHINES
dmi.board.version: V1.42
dmi.chassis.type: 1
dmi.chassis.vendor: EMACHINES
dmi.chassis.version: V1.42
dmi.modalias: dmi:bvnEMACHINES:bvrV1.42:bd06/11/2008:svneMachines:pneMachinesE510:pvrV1.42:rvnEMACHINES:rnRhine:rvrV1.42:cvnEMACHINES:ct1:cvrV1.42:
dmi.product.name: eMachines E510
dmi.product.version: V1.42
dmi.sys.vendor: eMachines

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

I have the same problem using udev 151-12.

I am facing same problem with CD/DVD.
If I place an working DVD movie) in DVD tray and close, system is not being able to identify and mount it.
# sudo ls -l /dvd/{cdrom,dvd}*
This returns nothing

If I place a blank DVD at the time of booting, udev somehow mounts the DVD after throwing lot of error. I can see /dev/sr0. Disk Utility reports the DVD drive correctly as:
HL-DT-ST DVDRAM GSA-T20N

But if I place a DVD with content then system does not detect the drive. /dev/sr0 does not show up under Disk Utility.

I am using udev ver 151.12.

dmesg and fstab is attached. Let me know what else do you need and how to get those diagnostic files.

I have AMD64 Alternate ISO installed. I have tested the beta 2 of the same and the DVD drive was working fine. It was working fine under Karmic AMD64 as well.

I have the same problem using udev 151-12 and Lucid 64 bits

I am using a fresh install of kubuntu 10.04 alternate installer downloaded 4th May, 32bit with 2 LG Multi DVD drives. If I put a DVD in, the device notifier pops up identifying the disk. If I open a file manager there is no sign of it. However, if I click on available actions in the device notifier and select open with a file manager then I can access it.

I have created fstab mount points and fiddled about with the automount settings in the device notifier but to no avail.
 I suspect this is why apt cannot fetch any packages from DVDs.

Can someonce help us? It feels crap to fall back to Vista (!!) just to play movies or listen to songs or anything to do with CD or DVD.

Sometimes I see the DVD drive, sometimes I don't. When I see the drive, everything works fine until the next boot, including playing movies. I don't know exactly what is making it disappear.
The udev version I have installed is 151-12, Ubuntu 10.04, and here is my dvdrw information, which I only see when my drive is detected: product: DVD+-RW GH50N; vendor: HL-DT-ST.

My workaround is to boot in recovery mode, and then "Proceed with normal boot". It looks like the drive is always detected when I do that. I end up at the terminal prompt. To open gnome, I login and type "startx".

Architecture: amd64
CustomUdevRuleFiles: 45-libnjb.rules 45-libmtp7.rules
DistroRelease: Ubuntu 10.04
MachineType: System manufacturer System Product Name
Package: udev 151-12
PackageArchitecture: amd64
ProcCmdLine: root=UUID=e26b529d-2477-4440-91be-255f5078d865 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-22-generic x86_64
UserGroups:

dmi.bios.date: 01/13/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A8V-E SE ACPI BIOS Revision 1010
dmi.board.name: A8V-E SE
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: ASUS
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8V-ESEACPIBIOSRevision1010:bd01/13/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTekComputerINC.:rnA8V-ESE:rvr1.XX:cvnASUS:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

In the Disk Utility, I see my drive (TSSTcorp CDW/DVD SH-M522C), but it won't mount.

It seems to be working OK for me now - I had tried to add some DVDs with apt, the first one was added OK, but it could't find anything on the second disk. When I looked in Dolphin (I'm using Kubuntu) it didn't have the Dist and Pool directories but was showing only the a-z folders subdirectory. When I put the third disk in it just showed some deb files, so it is not reading the directory structure properly.

When I removed the apt mount folder and rebooted and didn't put a repository disk in the drive then it appears to work OK with other disks. However, if I do put a repository disk in there then any subsequent disk isn't read properly if at all. It is as though apt mounts the drive then doesn't unmount it properly so it cannot be used for anything else.

So for me it seems as if apt is causing the problems.

I am having the same issue in Lucid and UDEV 151-12 on a PowerPC. The drive is visible in disk utility and properly identified via lshw but the media will not mount. Oddly enough, I can manage to get VLC to play music CDs (but not DVD video) even though disk utility has "no media detected".

I can successfully mount a CD from the terminal:

$ sudo mount /dev/hde /cdrom
mount: block device /dev/hde is write-protected, mounting read-only

I can also mount a video DVD in a similar manner. I'm not sure why they don't automount. I am fairly new to debugging - what additional information should I provide?

This is affecting me as well.... After reading through the messages I added these entries into my fstab...

/dev/sr0 /media/cdrom0 udf,iso9660 noauto,users 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 noauto,users 0 0

(yes I have two dvd/rw drives on a dell latitude laptop..)

Before adding the fstab entries, if I tried to run the Disk Utility, I would get an empty disk utility screen.. almost like it couldn't see the drives at all on the local machine.

Once I added the entries to /etc/fstab (shown above) (and created folders /media/cdrom0 and cdrom1)
Disk Utility then comes up with the proper screen showing the Harddrive, and both CD's, with one little quirk

Both ICONS for the drives (sr0 had a movie DVD in it & sr1 had 10.04 CD) look like regular CD's both drives appear to be readable as far as the file listing. but attempts to play the DVD caused "Unable to read from resource" error.

The CD appeared to read fine. It appears the DVD is not being distinguished as a DVD but rather a CD.

Hope this helps your investigation. Please let me know if you need any more information.

L8

The Gray Wizard
(aka: Matt)

I just found that I can plug in an external USB cd/dvd/rw and successfully automount both CDs and DVDs. So this is something that is only affecting my internal ATAPI Pioneer cd/dvd/rw.

This sounds like a problem I'm having excpet I'm using kubuntu 10.04 32 bit.
dolphin says "could not read" when using audio cd on /dev/sr0

using /dev/sr0:
audio cd could not read - dolphin
audio cd can read - k3b
data dvd-r can read - dolphin
data dvd-r can read - k3b

using /dev/sr1:
audio cd can read - dolphin
audio cd can read - k3b
data dvd-r can read - dolphin
data dvd-r can read - k3b

/dev-sr0 is a dvd rom
/dev/sr1 is a dvd rewritable
I'd like to be able to view audio cds using both drives.

When doing a sudo lshw -C disk

*-cdrom:0
       description: DVD reader
       product: DVD D DH16D2P
       vendor: ATAPI
       physical id: 0.0.0
       bus info: scsi@0:0.0.0
       logical name: /dev/cdrom1
       logical name: /dev/dvd1
       logical name: /dev/scd0
       logical name: /dev/sr0
       version: HP56
       capabilities: removable audio dvd
       configuration: ansiversion=5 status=ready
     *-medium
          physical id: 0
          logical name: /dev/cdrom1
  *-cdrom:1
       description: DVD-RAM writer
       product: DVD A DH20A4P
       vendor: ATAPI
       physical id: 0.1.0
       bus info: scsi@0:0.1.0
       logical name: /dev/cdrom
       logical name: /dev/cdrw
       logical name: /dev/dvd
       logical name: /dev/dvdrw
       logical name: /dev/scd1
       logical name: /dev/sr1
       version: 9P57

My drives were using cable select mode and I changed them to master and slave but I still can't read an audio cd in /dev/sr0.
I'm going to try adding the following to my fstab per nmgraywiz
/dev/sr0 /media/cdrom0 udf,iso9660 noauto,users 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 noauto,users 0 0

I just noticed two things that I have in common with the creator of this post and
I have an Asus motherboard also.

I still can't read an audio cd in /dev/sr0.
My motherboard is an Asus model P5GC MX/1333
with AMI bios 0413 date 03/13/09
My master drive is a lite on dvd rom
My slave drive is a lite on dvd-rw.
I'm tempted to try disconnecting the dvd-rw to see if that makes a difference.

Sorry, this is probably a hardware problem here. In case anybody reads my bogreport, I sent with ubuntu-bug. The malfunction might not actually be related to this bug for me, since I could read 4 CDs in a row without problems, but no other since then. I'm new to this, so I better tell you.

I have been watching this topic because it has been effecting me too. It was only effecting my internal dvd burner drive, but not my usb connected external dvd burner. I hae also exchange my internal drive with another computer's and that drive wouldn't mount either.

I believe the v2.6.32 kernels contain a bug that prevent some of us from mounting cds because it has been the case with me.
I tested 2 PPA kernels on Kubuntu Lucid today (fresh install for this test), creating cds and they worked as they should. They both allowed me to mount and dismount automatically, blank, burn iso's and data cds, and browse cds without problems. They are working fine with K3B, Dolphin, and the Device Notifier widget. I also rebooted several times to see if I would make the problem reappear, but it hasn't.

Kernels that won't mount my cd drive properly:
linux-image-generic-2.6.32.21.22
linux-image-generic-2.6.32.22.23

Working Kernels:
linux-image-2.6.33-02063301-generic_2.6.33-02063301_i386
(v2.6.33.1-lucid)
linux-image-2.6.34-020634-generic_2.6.34-020634_i386
(v2.6.34-lucid)

They can be found here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Possible solution:
I think we should move on to the v2.6.33 or greater kernels for Lucid.

My hardware:
$ sudo lshw -C disk
 *-cdrom
       description: DVD-RAM writer
       product: CDDVDW SH-S202J
       vendor: TSSTcorp
       physical id: 1
       bus info: scsi@3:0.0.0
       logical name: /dev/cdrom
       logical name: /dev/cdrw
       logical name: /dev/dvd
       logical name: /dev/dvdrw
       logical name: /dev/scd0
       logical name: /dev/sr0
       version: SB02
       capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
       configuration: ansiversion=5 status=ready
     *-medium
          physical id: 0
          logical name: /dev/cdrom

Set status to Confirmed, based on multiple reports in comments and people affected.

Interesting observation... it is only effecting my Ubuntu and Kubuntu 10.04 'installations', not the live cds.

Update: For about 2.5 days now, my dvd drive has been working perfectly in Ubuntu/Kubuntu Lucid (both live cds and installs). It mounts automatically and burns every time now. It is possible that my external drive was interfering with the performance of my internal dvd drive and also my wireless internet connection. There have been no problems with either ever since I disconnected the external drive. This problem only occurred in Ubuntu/Kubuntu with the 2.6.32.* kernels though. Newer PPA kernals had no problems in *ubuntu, as well as PClinuxOS 2010 and Windows XP.

this is affecting me as well....

Can confirm this problem (not like it needs confirmed anymore). Ubuntu and Kubuntu 10.04. Booting with a BLANK dvd in drive appears to solve problem but havent had a chance to text extensively (i fear the fdisk times on 2TB of data).

Can now confirm, upgrading to 2.6.3x kernel fixes problem (just upgraded to 2.6.35-2 based on previous suggestion)

I am running
Linux G4 2.6.32-22-powerpc-smp #36-Ubuntu SMP Fri Jun 4 00:04:49 UTC 2010 ppc GNU/Linux
and i still cannot mount a cd or dvd. I think this may be specific to PPC ports.

upgraded to 2.6.35-2 kernel, now DVD recognized but not mounted automatically

and erased DVD always not recognized

I am also having a problem after upgrading to 10.04. I can not mount cd/dvd's except under the following condition:
immediately after a reboot, and even then the disks will only stay mounted for a while before I start getting the "Buffer I/O error on device sr1, logical block 297861".
I have an ASUS P5N-E SLI motherboard. Several people have suggested that there may be a correlation with ASUS motherboards.

What I have tried...
1. Removing / adding / fiddling with fstab entries.
2. Reinstall entire operating system.
3. Changed order of boot devices in BIOS (from suggestion in the forums)
4. Ruled out hardware (drives working fine in WindowsXP). I have a dual boot setup.

Things to do:
Roll back to Karmic and verify that the drives start working again...

*-cdrom:0
       description: DVD-RAM writer
       physical id: 0.0.0
       bus info: scsi@5:0.0.0
       logical name: /dev/cdrom1
       logical name: /dev/cdrw1
       logical name: /dev/dvd1
       logical name: /dev/dvdrw1
       logical name: /dev/scd0
       logical name: /dev/sr0
       capabilities: audio cd-r cd-rw dvd dvd-r dvd-ram
       configuration: status=open
  *-cdrom:1
       description: DVD-RAM writer
       physical id: 0.1.0
       bus info: scsi@5:0.1.0
       logical name: /dev/cdrom
       logical name: /dev/cdrw
       logical name: /dev/dvd
       logical name: /dev/dvdrw
       logical name: /dev/scd1
       logical name: /dev/sr1
       capabilities: audio cd-r cd-rw dvd dvd-r dvd-ram
       configuration: status=open

Hi,

I am having the same issue with my cdrom drive and after 3 weeks of reading in the forum and trying out several steps I am pretty sure that it is hardware related, because:
Only by changing the CDROM DVD R/RW I got it working perfectly now.

the symptom in Ubuntu 10.04 (and also 9.10):
Cdrom is not recognized automatically, only in some seldom cases when I reboot the machine with CDROM placed already. But then I can not change the CD again, because it will not be recognized anymore (although lshw -disk shows the cdrom drive)

As it is reproduceable by exchanging only the CDROM hardware, I could send you the detailed hardware information and logs you need in order to track the issue down to the root cause. I have installed both UBUNTU versions in parallel; 10.04LTS 32bit and also 9.10 32bit. Both show same behavior with both CDROM Drives. so the issue is reproduceable. I can also try out latest kernel version (2.6.34 or 35), but I do not know whether this will help.

As I am not a Linux expert (but some shell scripting I know and also installing linux kernel via "apt-get" works fine) Can anyone send me the commands that I need to use in order to send you the information in order to track the issue down to its root cause?

The CDROM drive I changed was from "PLEXTOR PX716A" to a "NEC DVD_RW ND-1300A"
Cheers,

Similar problem here cd's either wont mount at all or mount immediately after booting system and then randomly unmount. Both my drives show up in Disk Utility and both drives work fine in Windows.

Installed Kernel 2.6.34 and this did not help.

q@q-desktop:~$ ls -l /dev/{cd,dvd}*
lrwxrwxrwx 1 root root 3 2010-06-17 09:44 /dev/cdrom -> sr0
lrwxrwxrwx 1 root root 3 2010-06-17 09:49 /dev/cdrom1 -> sr1
lrwxrwxrwx 1 root root 3 2010-06-17 09:44 /dev/cdrw -> sr0
lrwxrwxrwx 1 root root 3 2010-06-17 09:49 /dev/cdrw1 -> sr1
lrwxrwxrwx 1 root root 3 2010-06-17 09:44 /dev/dvd -> sr0

q@q-desktop:~$ sudo hdparm -I /dev/{sr0,sr1}

/dev/sr0:
 HDIO_DRIVE_CMD(identify) failed: Invalid exchange

/dev/sr1:
 HDIO_DRIVE_CMD(identify) failed: Invalid exchange

/dev/sr0:

ATAPI CD-ROM, with removable media
 Model Number: TSST CD-RW/DVD-ROM TSH492B
 Serial Number:
 Firmware Revision: TB04
Standards:
 Supported: CD-ROM ATAPI-1 -2 -3
Configuration:
 DRQ response: 50us.
 Packet size: 12 bytes
 cache/buffer size = unknown
Capabilities:
 LBA, IORDY(can be disabled)
 DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2
      Cycle time: min=120ns recommended=120ns
 PIO: pio0 pio1 pio2 pio3 pio4
      Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
 Enabled Supported:
      PACKET command feature set
      DEVICE_RESET command
    * DOWNLOAD_MICROCODE
      Removable Media Status Notification feature set
HW reset results:
 CBLID- above Vih
 Device num = 0
q@q-desktop:~$ sudo hdparm -I /dev/sr1

/dev/sr1:

ATAPI CD-ROM, with removable media
 Model Number: HL-DT-ST GCE-8320B
 Serial Number:
 Firmware Revision: 1.01
Standards:
 Likely used CD-ROM ATAPI-1
Configuration:
 DRQ response: 50us.
 Packet size: 12 bytes
 cache/buffer size = unknown
Capabilities:
 LBA, IORDY(cannot be disabled)
 DMA: mdma0 mdma1 *mdma2
      Cycle time: min=120ns recommended=120ns
 PIO: pio0 pio1 pio2 pio3 pio4
      Cycle time: no flow control=227ns IORDY flow control=120ns

Same issue here - USB sticks mount fine, CD-DRIVE won't mount on it's own. I have noticed that running KDE it works fine, only appears in the base gnome. This may have started after installing kubuntu on my machine for testing some things, I'm unsure.

Also, in the disk utility I can mount the drive just fine after putting a disc in. Also, when pressing eject on the drive, the tray comes out then immediately goes back in.

tony@river:~$ sudo hdparm -I /dev/sr0

/dev/sr0:

ATAPI CD-ROM, with removable media
 Model Number: ATAPI iHAS224 A
 Serial Number:
 Firmware Revision: ZL0P
 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6
Standards:
 Likely used CD-ROM ATAPI-1
Configuration:
 DRQ response: 50us.
 Packet size: 12 bytes
 cache/buffer size = unknown
Capabilities:
 LBA, IORDY(can be disabled)
 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
      Cycle time: min=120ns recommended=120ns
 PIO: pio0 pio1 pio2 pio3 pio4
      Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
 Enabled Supported:
    * PACKET command feature set
    * DEVICE_RESET command
    * Mandatory FLUSH_CACHE
    * Gen1 signaling speed (1.5Gb/s)
    * Phy event counters
      Device-initiated interface power management
    * Asynchronous notification (eg. media change)
    * Software settings preservation
tony@river:~$

More info. Running dmesg shows the following lines repeated 20 times or so when a disc is inserted:

[164525.734222] VFS: busy inodes on changed media or resized disk sr0
[164525.936364] VFS: busy inodes on changed media or resized disk sr0
[164526.021540] VFS: busy inodes on changed media or resized disk sr0
[164526.447405] VFS: busy inodes on changed media or resized disk sr0
[164526.660328] VFS: busy inodes on changed media or resized disk sr0
[164526.745497] VFS: busy inodes on changed media or resized disk sr0
[164527.171410] VFS: busy inodes on changed media or resized disk sr0

Had similar problem with my cdrom drive. Found the reason and solution to my problem here:
http://ubuntuforums.org/showthread.php?t=1025786

Solved my problem by removing the the udf from my /etc/fstab where my cdrom was mounted from:
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 to
/dev/scd0 /media/cdrom0 iso9660 user,noauto,exec,utf8 0 0

then remount your cdrom (e.g. mount /media/cdrom0)

Lucid is mounting with udf option in fstab.

Mounting the filesystem as iso9660 doesn't observe file permissions. Mounting as UDF does. Unfortunately, many disk burning applications leave -1 in the uid and gid permissions of their udf filesystems. This causes a permission problem in Linux.

The only way to read CD's as a user is by mounting UDF filesystems on cdrom as iso9660. Makes sense....

I've solveg updating to last kernel.

I've solved updating to last kernel.

There is a similar bug report for the PowerPC Ubuntu port located here:
https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/590448

In my case, forcing udev to poll for media immediately after it is loaded or ejected properly mounts the media and has the DVD or CD show up on the desktop. I currently do this by opening my CD/DVD/RW drive (which lshw shows as being at /dev/hde) using the following code:

eject -T && udisks --poll-for-media /dev/hde

I stuck it in a simple shell script that I can call from a panel applet when I need to load or eject a CD or DVD.

The latest kernel update did not help me, but since the PowerPC port is community supported, it lags behind the "official" kernel releases.

Updated to kernel 2.6.32-24, but the problem is still there: no cdrom/dvd drive mounted when inserting disk.

I also upgraded to 2.6.32-24-generic and still have the problem. I refuse to change hardware for this issue because both of my drives are identical and they both work perfectly using windowsXP. fstab tinkering has shown no promise.

I also have this problem with 2 different machines:
1. Newish Dell Vostro 1310. This will not mount any audio CDs with the internal drive or external USB drive. I have tried fiddling around with fstab and grub without success. I have also tried changing the bios setting from ACP to ATA. I I do have a copy of Mint 9 (32bit) running on VMPlayer on this machine which will successfully mount the CD. Here is what happens when I try to mount from the CLI:
~$ sudo mount /dev/sr0 /media/cdrom
mount: block device /dev/sr0 is write-protected, mounting read-only
mount: you must specify the filesystem type

Here is some other info
~$ sudo lshw -C disk
  *-cdrom
       description: DVD-RAM writer
       product: DVD+-RW DVW28SLC
       vendor: TEAC
       physical id: 0.0.0
       bus info: scsi@0:0.0.0
       logical name: /dev/cdrom
       logical name: /dev/cdrw
       logical name: /dev/dvd
       logical name: /dev/dvdrw
       logical name: /dev/scd0
       logical name: /dev/sr0
       version: A.06
       capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
       configuration: ansiversion=5 status=open

2. Old AMD 1600 system with ATA 33 interface this is running Mint 9 32bit. This will not mount the internal drive but will mount an external USB drive. I will post additional info from that machine.

This REALLY is irritating!

Could the proble be related to the IDE interface? I can't use both of my IDE CD/DVD drives, but I can use an external USB CD/DVD unit.

Architecture: amd64
CustomUdevRuleFiles: 10-vboxdrv.rules
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: udev 151-12
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=0128d8b5-091e-484a-8285-759d2956cd81 ro quiet splash pci=nomsi
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-24-generic x86_64
UserGroups: adm admin audio cdrom dialout lp lpadmin plugdev sambashare vboxusers
dmi.bios.date: 05/30/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MD-A72P-7509
dmi.board.vendor: XFX
dmi.board.version: Ver1.1
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnXFX:rnMD-A72P-7509:rvrVer1.1:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

OK! I have found a fix for this problem!!! (actually found the fix in one of the fedora forums)

Let me first clearly define the problem that I am fixing:

Conditions:

1. CD/DVD/CDR/CDRW disks "unmount" themselves shortly after mounting.

2. dmesg reports the following - VFS: busy inodes on changed media or resized disk sr0

3. I currently have no entries for either drive in /etc/fstab... The problem was exactly the same when I had the "/dev/sr0 /media/cdrom0 udf,iso9660 noauto,users 0 0" or similar lines in /etc/fstab.

4. Once one of the drives "unmounted", only a reboot would allow me to mount again.

5. All other devices and drives mount normally (and stay mounted with no issues)..

6. My relevant hardware is: Asus P5N-e motherboard,
cdrom:0 :: description: DVD-RAM writer :: product: CD/DVDW SH-S182D
cdrom:1 :: description: DVD-RAM writer :: product: CD/DVDW SH-S182D

Both drives are run off the secondary ide channel.

7. The hardware (motherboard and drives) is guranteed to be functional. I could not get either drive to fail in WindowsXP during overnight testing.

FIX::

Add "acpi=off" to the kernel load line in /boot/grub/grub.cfg then reboot... For example:
linux /boot/vmlinuz-2.6.32-24-generic root=UUID=c82dfc28-0bcf-48a6-995f-b61464bcf056 ro quiet splash acpi=off

I have gone through 2 days of stress testing the drives and neither has unmounted AND there are no more errors in dmesg...

TO DO:
1. Get more users to confirm this fix.
2. Submit the data to the ACPI team if it looks like the fix is repeatable.

Take care,
Sheldon

@Lord_Shadow. I have your same motherboard (P5NE-SLI) and I regret to say that I can't test your workaround, as the "acpi=off" setting disables my Logitech wireless Mouse/Keyboard, so I can't login! I reach the gdm login screen but there is nothing I can do than switch off the PC...

Sorry.

Hi Fabio,

Do you have a wired keyboard/mouse that you can use to test it out. If we can get you and a couple of other people to verify, then we can resubmit to the ACPI team..

Thanks,
Sheldon

Lord_Shadow,

I will look if I can find one in some of my drawers, but I don't want to fix a problem and create a new one! I need the cordless Logitech.

Same problem here but with an ASUS P5K-E motherboard. Turning off ACPI as Lord_Shadow suggested did NOT fix the problem, or at least only partially fixed it. With ACPI off I can mount CDROMs but I cannot mount/burn blank DVD-Rs.

As others have said, everything worked fine in Ubuntu 9.04, Ubuntu 9.10, and Windows XP.

@jplandry: there is already another bug about recognizing blank DVD and CD (bug 581925) and you can use Jonie's PPA to install patched udev. His PPA is https://launchpad.net/~jonie/+archive/ppa. Using this version worked for me.

Hello again all,

The 'acpi=off' fix that I listed above as a fix is no good... I had several days of flawless operation, but now the problem is back... I am not sure why I was able to work properly for a couple of days, but clearly this particular fix was not it. It may have been a coincidence or just dumb luck...

Anyway, I am rolling back to 9.10 right now. I will repost with the results later.

Sorry for the confusion,
Sheldon

Hello,

I have finished the roll back to 9.10 and the problem is completely gone (again). I played a DVD for 12 hours without any issues. I am not ready to call it fixed for another couple of days. I will check back after a few days.

Sheldon

Hello,

Like Lord Shadow I have an Asus P5NE SLI based system (PATA optical drive) (kernel 2.6.32-24 - 64bit)
Same problem:

Optical media not auto-mounted.
One time mount possible by leaving CD in drive when booting but disk only accessible for a while and then stops.

Rolled back to 9.10 and all is working (kernel 2.6.31-22 - 64bit)

Mike

Hi again,

Reporting back after a couple of weeks since switching back to 9.10 and I have not had a single instance of my optical drives failing to stay mounted. If there is anyone out there who needs any further information from me, or needs me to do any special testing, please let me know.

Sheldon

If you still have that problem on current 10.04 or 10.10, can you please add my sru-test PPA at

then upgrade your system (which will upgrade udev), and report back how it goes? If it still does not work, please describe the kind of medium which you inserted, open a terminal, and do

   sudo /lib/udev/cdrom_id --debug /dev/sr0

(with the medium inserted) and copy&paste the output. Thanks!

sorry: ... my PPA at https://launchpad.net/~pitti/+archive/sru-test

I still have thats problem won 10.10.
I install your sru-test PPA udev.

STEPS TO REPRODUCE:
   1. Place cd or dvd in disc drive, disc is recognized an mounted
   2. Eject disc
   3. (re)place same cd ord dvd in same disc drive and disc is recognized but not mounted

output :
main: probing: '/dev/sr0'
cd_inquiry: INQUIRY: [TSSTcorp][DVD-ROM SH-D163B][SB01]
cd_profiles: GET CONFIGURATION: size of features buffer 0x00a0
cd_profiles: GET CONFIGURATION: feature 'profiles', with 2 entries
feature_profiles: profile 0x10 dvd_rom
feature_profiles: profile 0x08 cd_rom
cd_profiles: GET CONFIGURATION: feature 0x0001 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0002 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0003 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0010 <ignored>, with 0x08 bytes
cd_profiles: GET CONFIGURATION: feature 0x001d <ignored>, with 0x00 bytes
cd_profiles: GET CONFIGURATION: feature 0x001e <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x001f <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0024 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x002a <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x002b <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x003b <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0100 <ignored>, with 0x00 bytes
cd_profiles: GET CONFIGURATION: feature 0x0103 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0104 <ignored>, with 0x00 bytes
cd_profiles: GET CONFIGURATION: feature 0x0105 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0106 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0107 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x010b <ignored>, with 0x04 bytes
cd_profiles: current profile 0x10
cd_profiles: profile 0x10 media_dvd_ro
cd_media_toc: READ TOC: len: 20, start track: 1, end track: 1
cd_media_toc: track=1 info=0x4(data) start_block=0
cd_media_toc: last track 1 starts at block 0
cd_media_info: disk type ff
cd_media_info: hardware reported media status: complete
ID_CDROM=1
ID_CDROM_CD=1
ID_CDROM_DVD=1
ID_CDROM_MEDIA=1
ID_CDROM_MEDIA_DVD=1
ID_CDROM_MEDIA_STATE=complete
ID_CDROM_MEDIA_SESSION_COUNT=1
ID_CDROM_MEDIA_TRACK_COUNT=1
ID_CDROM_MEDIA_TRACK_COUNT_DATA=1

FrenchNux,

this cdrom_id output looks fine. Was that at the time when you had the second DVD inserted, and with the udev from my PPA? Did that change anything? Can you please revert to the previous udev with

  sudo apt-get install udev/maverick

and doing the cdrom_id output again, in the same situation?

Hello,

i tested with udev sru-test ppa and output after second inserted.
I compared output after 1st inserted and 2nd inserted it seems the same

output with maverick udev package :
main: probing: '/dev/sr0'
cd_inquiry: INQUIRY: [TSSTcorp][DVD-ROM SH-D163B][SB01]
cd_profiles: GET CONFIGURATION: size of features buffer 0x00a0
cd_profiles: GET CONFIGURATION: feature 'profiles', with 2 entries
feature_profiles: profile 0x10 dvd_rom
feature_profiles: profile 0x08 cd_rom
cd_profiles: GET CONFIGURATION: feature 0x0001 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0002 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0003 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0010 <ignored>, with 0x08 bytes
cd_profiles: GET CONFIGURATION: feature 0x001d <ignored>, with 0x00 bytes
cd_profiles: GET CONFIGURATION: feature 0x001e <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x001f <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0024 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x002a <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x002b <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x003b <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0100 <ignored>, with 0x00 bytes
cd_profiles: GET CONFIGURATION: feature 0x0103 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0104 <ignored>, with 0x00 bytes
cd_profiles: GET CONFIGURATION: feature 0x0105 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0106 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x0107 <ignored>, with 0x04 bytes
cd_profiles: GET CONFIGURATION: feature 0x010b <ignored>, with 0x04 bytes
cd_profiles: current profile 0x10
cd_profiles: profile 0x10 media_dvd_ro
cd_media_toc: READ TOC: len: 20
cd_media_toc: track=1 info=0x4(data) start_block=0
cd_media_toc: last track 1 starts at block 0
cd_media_info: disk type ff
cd_media_info: hardware reported media status: complete
ID_CDROM=1
ID_CDROM_CD=1
ID_CDROM_DVD=1
ID_CDROM_MEDIA=1
ID_CDROM_MEDIA_DVD=1
ID_CDROM_MEDIA_STATE=complete
ID_CDROM_MEDIA_SESSION_COUNT=1
ID_CDROM_MEDIA_TRACK_COUNT=1
ID_CDROM_MEDIA_TRACK_COUNT_DATA=1

Thanks, so it's not due to cdrom_id, that seems to work just fine; I need more logs for this, I'm afraid. Can you please run "ubuntu-bug storage" and follow the interactive dialogs? This will collect all the useful logs which I need to track this problem.

Since this will create a new bug report, I am closing this one (but please feel free to post the but number here, so that I can see the other one quickly). Thank you!

i create Bug #658283
i hope you have al what you want

2010/10/11 Martin Pitt <email address hidden>

> Thanks, so it's not due to cdrom_id, that seems to work just fine; I
> need more logs for this, I'm afraid. Can you please run "ubuntu-bug
> storage" and follow the interactive dialogs? This will collect all the
> useful logs which I need to track this problem.
>
> Since this will create a new bug report, I am closing this one (but
> please feel free to post the but number here, so that I can see the
> other one quickly). Thank you!
>
> ** Changed in: udev (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> Cdrom drive not recognized automatically
> https://bugs.launchpad.net/bugs/562092
> You received this bug notification because you are a direct subscriber
> of the bug.
>

ok Bug #658377 is created

2010/10/11 Christophe PAUC <email address hidden>

> i create Bug #658283
> i hope you have al what you want
>
> 2010/10/11 Martin Pitt <email address hidden>
>
> Thanks, so it's not due to cdrom_id, that seems to work just fine; I
>> need more logs for this, I'm afraid. Can you please run "ubuntu-bug
>> storage" and follow the interactive dialogs? This will collect all the
>> useful logs which I need to track this problem.
>>
>> Since this will create a new bug report, I am closing this one (but
>> please feel free to post the but number here, so that I can see the
>> other one quickly). Thank you!
>>
>> ** Changed in: udev (Ubuntu)
>> Status: Incomplete => Invalid
>>
>> --
>> Cdrom drive not recognized automatically
>> https://bugs.launchpad.net/bugs/562092
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

For me this bug has been solved after upgrading to Meerkat. Thanks for looking into this.