CD/RW Mount Problems with Intrepid

Here is the Dmesg output:-

DISC MADE WITH CD/DVD CREATOR....

$ dmesg | grep sr0
[ 8.733619] sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
[ 8.733900] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 207.333693] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 207.333717] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 207.333729] sr 1:0:0:0: [sr0] Add. Sense: No seek complete
[ 207.333741] end_request: I/O error, dev sr0, sector 1426944
[ 207.333763] Buffer I/O error on device sr0, logical block 356736
[ 213.538750] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 213.538774] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 213.538786] sr 1:0:0:0: [sr0] Add. Sense: No seek complete
[ 213.538798] end_request: I/O error, dev sr0, sector 1426948
[ 213.538815] Buffer I/O error on device sr0, logical block 356737
[ 225.709364] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 225.709388] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 225.709400] sr 1:0:0:0: [sr0] Add. Sense: No seek complete
[ 225.709412] end_request: I/O error, dev sr0, sector 1427064
[ 225.709428] Buffer I/O error on device sr0, logical block 356766
[ 233.273650] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 233.273674] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 233.273686] sr 1:0:0:0: [sr0] Add. Sense: No seek complete
[ 233.273698] end_request: I/O error, dev sr0, sector 1427064
[ 233.273714] Buffer I/O error on device sr0, logical block 356766

DISK MADE WITH BRASERO............ ( which eventually mounted this time????? )

$ dmesg | grep sr0
.........
[ 325.243608] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 325.243632] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 325.243644] sr 1:0:0:0: [sr0] Add. Sense: No seek complete
[ 325.243656] end_request: I/O error, dev sr0, sector 1431040
[ 325.243670] Buffer I/O error on device sr0, logical block 178880
[ 331.419570] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 331.419593] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 331.419606] sr 1:0:0:0: [sr0] Add. Sense: No seek complete
[ 331.419617] end_request: I/O error, dev sr0, sector 1431040
[ 331.419633] Buffer I/O error on device sr0, logical block 178880
[ 337.630370] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 337.630393] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 337.630406] sr 1:0:0:0: [sr0] Add. Sense: No seek complete
[ 337.630417] end_request: I/O error, dev sr0, sector 1431168
[ 337.630432] Buffer I/O error on device sr0, logical block 178896
[ 346.511998] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 346.512034] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 346.512047] sr 1:0:0:0: [sr0] Add. Sense: No seek complete
[ 346.512059] end_request: I/O error, dev sr0, sector 1431176
[ 346.512075] Buffer I/O error on device sr0, logical block 178897

Now not sure if this IS a Brasero problem.....

Have just performed a clean install of Intrepid ( including re-format of the hard drive ) and the problem still exists, so it does NOT appear to be a problem concerned with the upgrade process.

Same problem on a Dell notebook, upgraded from 8.04. Any cd would mount on 8.04 but with intrepid it seems that every disc burned with brasero cannot be mounted giving similar errors as the above on the system log. Same cd mounts ok on another pc with 8.04 installed and on windows xp.

Same problem on a Lenovo 3000 n100. Anything would mount just fine in Hardy; in Intrepid - and only started some time after my upgrade - it does not mount audio cd's, and sometimes it can mount data CD but cannot write to it. Tried using both Brasero and K3b. Ubuntu says it cannot mount my audio cd, because the device /dev/scd0 cannot be found. The drive is listed in /dev, and if it couldn't find it, why would it be able to recognize an audio CD from any other CD? Trying to mount my cd manually using "mount -t auto", it says I need to specify the fstype. What fstype is used on an ordinary audio CD?

Here's a screenshot of the message I get - it's in Danish, but it says "Unable to mount audio CD / cannot find drive /dev/scd0"

Same problem here on an AMD64 (running 64 bit). Worked fine with Hardy, worked ok after upgrade to intrepid, and then sometime within the last 2 weeks it has just stopped working. I am assuming it was a recent update that broke it.

Symptoms: refuses to mount audio CD's, DVD drive refuses to respond to eject button too (not sure if this is related though as I haven't used it in a while).

Another side issue that may be related is that I tried using all the different CD burner applications after intrepid upgrade and none of them appeared to work and most told me I didn't have any CD/DVD drives which is odd.

I have the same problem on my desktop's IDI-DVD ROM 6116 drive. However, the problem does not occur on that same desktop's TSSTcorp CD/DVDW SH-S182D drive. Nor does it occur on my laptop's HL-DT-ST RW/DVD GCC-4247 ATA drive or on my girlfriend's laptop's PIONEER DVD-RW DVR-K14 drive.
So it's definitely something with the drive...

I have the same problems my CD/DVDW TS-H552B. No problems with past ubuntu versions. Only don't wok with Intrepid.

messages logs.

Nov 15 21:04:16 deflagmator kernel: [ 653.085509] sr 5:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
Nov 15 21:04:16 deflagmator kernel: [ 653.085526] sr 5:0:0:0: [sr0] Sense Key : Hardware Error [current]
Nov 15 21:04:16 deflagmator kernel: [ 653.085539] sr 5:0:0:0: [sr0] Add. Sense: Timeout on logical unit

No problems with the other IDE ASUS reader DVD-E616P3H

        *-cdrom:0
             description: DVD writer
             product: CD/DVDW TS-H552B
             vendor: TSSTcorp
             physical id: 0.0.0
             bus info: scsi@5:0.0.0
             logical name: /dev/cdrom2
             logical name: /dev/cdrw2
             logical name: /dev/dvd2
             logical name: /dev/dvdrw2
             logical name: /dev/scd0
             logical name: /dev/sr0
             version: HP13
             capabilities: removable audio cd-r cd-rw dvd dvd-r
             configuration: ansiversion=5 status=ready
           *-medium
                physical id: 0
                logical name: /dev/cdrom2

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need more information.

Please follow the "How to file" procedure described at https://wiki.ubuntu.com/DebuggingHal and attach the requested files here. Be sure to attach -not paste- the requested files to keep this bug report readable. Also, please attach each file separately and uncompressed. Please don't tar or zip them together. Please don't tar or zip each file.

Please be aware that a bug subscribed to by many people (like this one) may actually be different bugs showing the same symptoms. If during the course of investigation, your problem diverges from this bug, then please feel free to open a new bug on the topic and move the discussion on your problem to the new bug report. We prefer to keep bug reports to a single issue; that way everyone can tell when the issue is fixed.

Ok here is.

After some minutes of attempts to mount the cdrom nautilus shows the name of the cd and the contents. Then I can use the data (copy for example) with no errors.

If I extract the cd and insert it again it takes the same time after some error messages (DBUS) to appear in nautilus.

This happens always with the same CD-ROMS. There is some other CD-Roms that don't have problems to mount.

(but I repeat, this only happens in Intrepid) (If I reboot in hardy I don't have problems.)

Sorry my poor english

hal log - rebooted system, put in cd, started rhythmbox, all looked ok, ejected tried another, still looked ok.

I do not understand what is going on here, I rebooted endlessly yesterday trying to get this to work and suddenly it sparks back into life when I debug it.

kernel log - rebooted system, put in cd, started rhythmbox, all looked ok, ejected tried another, still looked ok.

I do not understand what is going on here, I rebooted endlessly yesterday trying to get this to work and suddenly it sparks back into life when I debug it.

and finally, lshal.txt

Subsequent to my debug session I have just tried to rip 5 or 6 CD's using Rhythmbox. On Hardy this was never any bother but I am getting crashes every couple of CD's I put in Rhythmbox just exits with no information at all. At present when I restart it all works fine again, I am guessing that maybe when it crashes it could potentially leave things in broken state but it has not occured so far.

Sorry for any delay, I have just returned from holiday.

I have recreated the original problem by inserting a CD burnt using Brasero on Hardy 8.04. When the disc is inserted I get the message that it is unable to mount, however 2 minutes later it will appear mounted on the desktop and all the files are readable.

.....and finally Kern.log.

By the way, before going on holiday, I re-checked both the Live Install and Alternate CDs that I had burnt from images obtained using the Transmission BitTorrent Client (and had assumed would be checked against the image held by the Tracker). It turns out that BOTH discs reported incorrect md5sums.

I have read in one of the Ubuntu forums that there may have been a problem with some of the images being distributed on the day of Intrepid 8.10's release, and this seems to have been the case. I have since downloaded a new image of the Live Install CD, burnt it to disc, checked it and the md5sum is good.

I will perform another clean install with this soon and post the results.

I am also experiencing a problem mounting data discs in 8.10.

Having recently changed from Suse 10.3/KDE to Ubuntu 8.10/Gnome I have discs burnt with Suse/K3b. These discs mount very, very slowly with much disc activity using 8.10.

Discs burnt with Brasero behave in a similar manner. However discs written with the same files using Disc Creator mount quickly and reliably.

When the mount is giving trouble I the following repeated many times over in the logs:

Mar 6 15:23:10 dart kernel: [18011.130487] sr 4:0:0:0: [sr0] Sense Key : Medium Error [current]
Mar 6 15:23:10 dart kernel: [18011.130500] sr 4:0:0:0: [sr0] Add. Sense: No seek complete
Mar 6 15:23:17 dart kernel: [18018.126718] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
Mar 6 15:23:17 dart kernel: [18018.126736] sr 4:0:0:0: [sr0] Sense Key : Medium Error [current]
Mar 6 15:23:17 dart kernel: [18018.126749] sr 4:0:0:0: [sr0] Add. Sense: No seek complete
Mar 6 15:23:18 dart kernel: [18018.437012] cdrom: sr0: mrw address space DMA selected
Mar 6 15:23:25 dart kernel: [18025.482751] sr 4:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK

Hardware is an Asus M2NPV-MX with an Athlon 64 X2 4800+

I'm seeing similar issues accessing CD-Rs here on a Hardy box (8.04.1), but I've just tried updating to the latest kernel in -updates and no joy:

[ 4697.036353] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
[ 4697.036365] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 4697.036369] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error
[ 4697.036376] end_request: I/O error, dev sr0, sector 305520
[ 4697.036382] Buffer I/O error on device sr0, logical block 76380
[ 4697.573531] end_request: I/O error, dev sr0, sector 305512
[ 4697.573543] Buffer I/O error on device sr0, logical block 76378
[ 4697.573550] Buffer I/O error on device sr0, logical block 76379

The numbers shown here actually don't make any sense; according the disc TOC the disc is 76229 *sectors* long, and that's consistent with amount of data I wrote to it (~150Mbytes.)

The disk *does* eventually mount, so obviously the problem obviously isn't critical. Adding an explicit "-t iso9660" to my mount command speeds things up nicely, so obviously it's something to do with the filesystem type probe?

Aha .. inspiration. I'm mounting manually ("mount /dev/cdrom /cdrom", a mental regression to the days before /media/xxx!). If I do "mount /media/cdrom0", everything is fine, presumably because my fstab has:

/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

I'm guessing that some of the file system type probes that mount does are causing the problem? /cdrom is a symlink to /media/cdrom, and /media/cdrom is a symlink to /media/cdrom0, so maybe the problem being seen is related to a change to either:

(A) symlink resolution when trying to match mount command line options to /etc/fstab, or
(B) the file system type probe process run by mount, which, according to the man-page, is:

"If no -t option is given, or if the auto type is specified, mount will try to guess the desired type.
Mount uses the blkid or volume_id library for guessing the filesystem type; if that does not turn up any‐
thing that looks familiar, mount will try to read the file /etc/filesystems, or, if that does not exist,
/proc/filesystems. All of the filesystem types listed there will be tried, except for those that are
labeled "nodev" (e.g., devpts, proc and nfs). If /etc/filesystems ends in a line with a single * only,
mount will read /proc/filesystems afterwards."

Any help to anybody?

Looking more closely at some of the comments here:

alanmilne: your problem looks like it might also be a type probe issue - the ratio between the sector and block numbers in your dmesg output suggest a filesystem that is expecting 4 sectors / block, for whatever definition of "block" is in use here (1K? 4K?) I don't entirely understand why the burning application should make a difference..

lusepuster: sounds like you might have a different problem (hardware? some other hal issue - bug #218834 maybe?) Audio CDs aren't mounted, and use a different sector format ("red book" versus "yellow book", IIRC)

Taygeto: I have another hardy machine where I can do "mount /dev/cdrom /cdrom" without the errors I reported above, though that machine is 8.04.2. Maybe the ata drivers or the drives themselves handle accesses beyond the end of the media differently? I was using an unclosed (= appendable) disk here too, which may be another issue: maybe that also explains why the burning application makes a difference (does one always leave the disc open maybe?)

I initially thought the burning program made a difference (perhaps something to do with the disc format) but now I suspect it is just an intermittent problem.

One of the discs I had trouble with now mounts quickly with the automounter.

When it mounts I now see the following in the messages log:

Mar 17 17:35:50 dart kernel: [ 2851.200673] cdrom: sr0: mrw address space DMA selected
Mar 17 17:35:50 dart kernel: [ 2851.202951] cdrom open: mrw_status 'not mrw'
Mar 17 17:35:50 dart kernel: [ 2851.241371] cdrom: sr0: mrw address space DMA selected
Mar 17 17:35:50 dart kernel: [ 2851.243597] cdrom open: mrw_status 'not mrw'
Mar 17 17:35:50 dart kernel: [ 2851.366621] UDF-fs: No VRS found

.......... Is this normal behaviour?

On Tue, Mar 17, 2009 at 05:38:30PM -0000, Richard Driscoll wrote:

> Mar 17 17:35:50 dart kernel: [ 2851.200673] cdrom: sr0: mrw address space DMA selected
> Mar 17 17:35:50 dart kernel: [ 2851.202951] cdrom open: mrw_status 'not mrw'
> Mar 17 17:35:50 dart kernel: [ 2851.241371] cdrom: sr0: mrw address space DMA selected
> Mar 17 17:35:50 dart kernel: [ 2851.243597] cdrom open: mrw_status 'not mrw'
> Mar 17 17:35:50 dart kernel: [ 2851.366621] UDF-fs: No VRS found
>
> .......... Is this normal behaviour?

I think this just means the disk is not formatted for packet writing
(MRW = "Mount rainier Read/Write", apparently.)

Maybe this is a different problem to what I was seeing -- after all,
everybody else saw it after upgrading to 8.10, I'm seeing it in 8.04.
The parallels seemed pretty close, though, and a backported update could
explain me seeing it in Hardy ..

Next time you have problems, you could try explicitly mounting it from
the command line ("mount /dev/cdrom -t iso9660") and see if that helps..

S.

I'm only talking about data CDs here.

With Steve's help I think I've identified the problem (at least in my case). The slow automounts only happen with multisession CDs which have more than one session recorded on them.

It seems that the Nautilus CD creator never writes multisession.

Brasero is strange. If you insert a multisession disc you are able to add to it using "import session," but I just cannot get it to start a mutisession from a blank (or just erased) disc. I read somewhere that there is supposed to be an option to "leave the disc open" but I just can't find it.

K3b seems to be able to do whatever you like - start multission or not and close or continue multisession.

Can anyone else confirm this behaviour (especially the mounting issues)?

Oh I forgot. The discs can always be mounted manually with the following in fstab:-

/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

I think that the installation put the line there.

stracing my problematic mount command shows that the problems occur when then mount process itself is trying to access the block device, not in e.g. a mount syscall. I'm guessing that this is a (statically linked) libvolume-id trying to the determine the filesystem type?

(Incidentally, the machine I'm having problems on has mount 2.13.1-5ubuntu2 (Hardy 8.04.1); my 8.04.2 box with mount 2.13.1-5ubuntu3 is OK. The changelog mentions nothing relevant - was it built against a different libvolume-id perhaps?)

I don't know if the problems seen on the desktop using intrepid are down to udev, hal, gnome-vfs or mount.. Anybody care to take a guess?

Incidentally, I added the linux package when this was looking like a kernel bug. Anyone have any objections if I remove it?

I'm getting the same problem (I think), so far it only seems to be CD-RW disks that have trouble reading. It doesn't pick up media at all in the drive, so I can't erase or do anything with it. I can't mount it manually, because the system can't seem to find media to mount. Normal CD-ROM's and CD-R's seem to be fine, as are all DVD's (except my system doesn't seem to be able to write to DVD+R's, even though DVD+RW is fine, WTF? :s). Worked in Hardy though on the same machine, just hasn't worked since upgrading to Intrepid.

I have had this problem since Hardy. I am dual booting 7.10 still until they fix it. Every thing is working fine in Gutsy.

I had similar problems, but they nseem to have gone in version 9.04 Jaunty

I have a fresh install of Jaunty done just yesterday. I decided to reinstall it since my dual boot gives access to my data partition. Same problem. Since 7.10 works flawlessly at burning and detecting the disks. My back up computer running Intrepid works fine also. This is very reminiscent of a different OS that not too many people liked. You know the old OS works fine on your hardware but the new one doesn't. I love Ubuntu. I am anxiously awaiting someone to take this serious. It is hard to turn people on to something that does not work right. It makes all those of us that advocate for Ubuntu look foolish.

this fix worked for me:
 Re: 9.04 cannot mount CD/DVD drive.
retiredtechie
I finally got mine working by editing fstab after finding the fix in a google search.

Code:

sudo gedit /etc/fstab
<password>

# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=97f48878-4b54-484c-8a4e-4fa11aa9c2fc / ext3 relatime,errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=9f6f9e31-e4ff-4dd6-8622-a8d26b433d5f none swap sw 0 0
# Original setting
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

Note the /dec/scd0 line above. Exchange the positions of udf,iso9660 like this:

Code:

# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=97f48878-4b54-484c-8a4e-4fa11aa9c2fc / ext3 relatime,errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=9f6f9e31-e4ff-4dd6-8622-a8d26b433d5f none swap sw 0 0
# Revised setting to allow reading Windows formatted CDs and DVDs
/dev/scd0 /media/cdrom0 iso9660,udf user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

Save the file. I think you may have to reboot to make it work, can't remember. Good luck.
link: http://ubuntuforums.org/showthread.php?p=7556471#post7556471

Hmm, that definitely points to a filesystem type probe issue, and judging by <http://ubuntuforums.org/showpost.php?p=7453864&postcount=26>, there may be something to do with symlink resolution going on as well (at least on my machine, /dev/sr0 is a symlink to /dev/scd0.)

Anybody who knows the code care to comment?

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

http://www.freedesktop.org/wiki/Software/hal/