CD/DVD burning problem in hardy

Bug #200337 reported by Wouter Stomp
100
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Gentoo Linux
Unknown
Medium
brasero (Ubuntu)
Invalid
Undecided
Unassigned
dvd+rw-tools (Ubuntu)
Opinion
Low
Unassigned
k3b (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Medium
Stefan Bader
nautilus-cd-burner (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Hi im new at linux but i'm trying to do my best with the best system there is ;) ...

I had a problem burning DVDs it kept on giving me an error it didnt want to burn anything then i try to lower the speed of the burning process wich by default is "maximun speed possible" always. I changed the burning speed to to 2x and it started working again ... I really dont know why cause i dont know how to use linux very well but it seems the problems is that there is a conflict with the decision on speed when is left to system to decide by itself ...

well those are my two cents i hope if someone reads this knows how to fix the bug

Andy Bartolme
Dominican Republic

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Binary package hint: nautilus-cd-burner

Burning cd's and dvd's is currently not working in hardy for me, while it worked perfectly on gutsy. I tried both nautilus-cd-burner and brasero. When I use n-c-b it finishes very quickly, but it seems only the file/directory strucure is written to disc, but none of the actual data. I think (but I am not completely sure) that this started around the time of the GVFS updates several weeks ago.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Could you run gconf-editor, enable the apps, nautilus-cd-burner, debug key, starts nautilus on a command line and copy there the log when trying to burn something?

Changed in nautilus-cd-burner:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

I first tried starting n-c-b from the command-line, that doesn't work because it says no files selected. I then runned nautilus from the command line and went to burn:/// to write a disc. I get this error again:

Error writing to disc
There was an error writing to the disc:
Unhandled error, aborting

There is no output displayed at the command line. Is it written to a log file somewhere? I couldn't find it.

Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :
Download full text (3.6 KiB)

Ah, it works when you first use burn:/// to compile the cd and then start n-c-b from the command line (that cost me another dvd to find out :-( ). I get the following output:

launching command: growisofs -dvd-compat -graft-points -path-list /tmp/iso-wouter.BLFS7T -Z /dev/hdc -input-charset utf8 -r -J -V Personal Data, mrt 14, 2008
growisofs stdout: Executing 'genisoimage -graft-points -path-list /tmp/iso-wouter.BLFS7T -input-charset utf8 -r -J -V Personal Data, mrt 14, 2008 | builtin_dd of=/dev/hdc obs=32k seek=0'
growisofs stderr: Using SPANI000.MP3;1 for /spanishpod_E0084pr.mp3 (spanishpod_E0080pr.mp3)
growisofs stderr: Using SPANI001.MP3;1 for /spanishpod_E0080pr.mp3 (spanishpod_E0074pr.mp3)
growisofs stderr: Using SPANI002.MP3;1 for /spanishpod_E0074pr.mp3 (spanishpod_E0070pr.mp3)
growisofs stderr: Using SPANI003.MP3;1 for /spanishpod_E0070pr.mp3 (spanishpod_E0064pr.mp3)
growisofs stderr: Using SPANI004.MP3;1 for /spanishpod_E0064pr.mp3 (spanishpod_E0060pr.mp3)
growisofs stderr: Using SPANI005.MP3;1 for /spanishpod_E0060pr.mp3 (spanishpod_D0085pr.mp3)
growisofs stderr: Using SPANI006.MP3;1 for /spanishpod_D0085pr.mp3 (spanishpod_D0077pr.mp3)
growisofs stderr: Using SPANI007.MP3;1 for /spanishpod_D0077pr.mp3 (spanishpod_D0075pr.mp3)
growisofs stderr: Using SPANI008.MP3;1 for /spanishpod_D0075pr.mp3 (spanishpod_D0067pr.mp3)
growisofs stderr: Using SPANI009.MP3;1 for /spanishpod_D0067pr.mp3 (spanishpod_D0065pr.mp3)
growisofs stderr: Using SPANI00A.MP3;1 for /spanishpod_D0065pr.mp3 (spanishpod_D0057pr.mp3)
growisofs stderr: Using SPANI00B.MP3;1 for /spanishpod_D0057pr.mp3 (spanishpod_D0053pr.mp3)
growisofs stderr: Using SPANI00C.MP3;1 for /spanishpod_D0053pr.mp3 (spanishpod_D0048pr.mp3)
growisofs stderr: Using SPANI00D.MP3;1 for /spanishpod_D0048pr.mp3 (spanishpod_D0042pr.mp3)
growisofs stderr: Using SPANI00E.MP3;1 for /spanishpod_D0042pr.mp3 (spanishpod_D0038pr.mp3)
growisofs stderr: Using SPANI00F.MP3;1 for /spanishpod_D0038pr.mp3 (spanishpod_C0083pr.mp3)
growisofs stderr: Using SPANI00G.MP3;1 for /spanishpod_C0083pr.mp3 (spanishpod_C0078pr.mp3)
growisofs stderr: Using SPANI00H.MP3;1 for /spanishpod_C0078pr.mp3 (spanishpod_C0073pr.mp3)
growisofs stderr: Using SPANI00I.MP3;1 for /spanishpod_C0073pr.mp3 (spanishpod_C0068pr.mp3)
growisofs stderr: Using SPANI00J.MP3;1 for /spanishpod_C0068pr.mp3 (spanishpod_C0063pr.mp3)
growisofs stderr: Using SPANI00K.MP3;1 for /spanishpod_C0063pr.mp3 (spanishpod_C0058pr.mp3)
growisofs stderr: Using SPANI00L.MP3;1 for /spanishpod_C0058pr.mp3 (spanishpod_C0055pr.mp3)
growisofs stderr: Using SPANI00M.MP3;1 for /spanishpod_C0055pr.mp3 (spanishpod_C0050pr.mp3)
growisofs stderr: Using SPANI00N.MP3;1 for /spanishpod_C0050pr.mp3 (spanishpod_C0045pr.mp3)
growisofs stderr: Using SPANI00O.MP3;1 for /spanishpod_C0045pr.mp3 (spanishpod_C0043pr.mp3)
growisofs stderr: Using SPANI00P.MP3;1 for /spanishpod_C0043pr.mp3 (spanishpod_C0040pr.mp3)
growisofs stderr: Using SPANI00Q.MP3;1 for /spanishpod_C0040pr.mp3 (spanishpod_C0032pr.mp3)
growisofs stderr: Using SPANI00R.MP3;1 for /spanishpod_C0032pr.mp3 (spanishpod_C0028pr.mp3)
growisofs stderr: Using SPANI00S.MP3;1 for /spanishpod_C0028pr.mp3 (spani...

Read more...

Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

Don't know if it helps, but my cd burner is an AOpen DUW1608/ARR.

Changed in nautilus-cd-burner:
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

seems to be a linux or cdrecord issue rather than gnome one

Changed in nautilus-cd-burner:
assignee: desktop-bugs → nobody
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Wouter,

If you aren't already doing so, care to test with the latest 2.6.24-12 kernel. Then assuming the issue still exists, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux:
status: New → Incomplete
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

Yes, this occurred using the 2.6.24-12 kernel.

Changed in linux:
status: Incomplete → New
Changed in linux:
assignee: nobody → ubuntu-kernel-team
status: New → Triaged
Revision history for this message
emmanuel (le-unamme) wrote :

I have the same problem I think, after a fresh install, i'm unable to burn even with brasero, or nautilus-cd-burner, or gnomebaker, the debug output of nautilus cd burner is :

manu@manu-desktop:~$ nautilus-cd-burner
launching command: growisofs -dvd-compat -use-the-force-luke=tty -graft-points -path-list /tmp/iso-manu.JKN87T -Z /dev/scd1 -input-charset utf8 -r -J -V Données perso, 24 mar 2008
growisofs stderr: WARNING: /dev/scd1 already carries isofs!
growisofs stdout: About to execute 'genisoimage -graft-points -path-list /tmp/iso-manu.JKN87T -input-charset utf8 -r -J -V Données perso, 24 mar 2008 | builtin_dd of=/dev/scd1 obs=32k seek=0'
growisofs stderr: 1.43% done, estimate finish Mon Mar 24 20:08:54 2008
growisofs stderr: 2.85% done, estimate finish Mon Mar 24 20:08:54 2008
growisofs stderr: 4.28% done, estimate finish Mon Mar 24 20:08:54 2008
growisofs stderr: /dev/scd1: restarting DVD+RW format...
growisofs stderr: /dev/scd1: "Current Write Speed" is 4.1x1352KBps.
growisofs stderr: :-[ WRITE@LBA=20h failed with SK=4h/ASC=08h/ACQ=03h]: Input/output error
growisofs stderr: :-( write failed: Input/output error
growisofs stderr: /dev/scd1: flushing cache
growisofs stderr: /dev/scd1: writing lead-out
process stdout: HUP
process stderr: HUP

Revision history for this message
Bassem JARKAS (jarkas) wrote :

The same problem here ...
i was able to burn DVDs on ubuntu 7.10 , but after upgrading to Hardy it failed.
this is gnomebaker output:

Executing 'genisoimage -gui -V GnomeBaker data disk -A GnomeBaker -p Bassem -iso-level 3 -l -r -hide-rr-moved -J -joliet-long -graft-points --path-list /tmp/gnomebaker-EKEK8T | builtin_dd of=/dev/sr0 obs=32k seek=0'
I: -input-charset not specified, using utf-8 (detected in locale settings)
/dev/sr0: "Current Write Speed" is 4.1x1352KBps.
:-[ WRITE@LBA=20h failed with SK=4h/ASC=08h/ACQ=03h]: Input/output error
:-( write failed: Input/output error
/dev/sr0: flushing cache
/dev/sr0: updating RMA
/dev/sr0: closing session

Revision history for this message
Tom (tomasz-belina) wrote :

Problem still exists. I use kernel 2.6.24-16.30-generic.

Revision history for this message
OberonKing (oberonking) wrote :

same here, i'm in Hardy... fresh install, but I have this issue since Feisty and never have a fix for that. well in Feisty/Gusty I turn of dma for device with hdparm and burn ok, in Hardy I cant turn of that.... the system take the IDE device has a SCSI device, and this there isn't dma.

My device is an Asus DRW-1608P2.... in others OS works fine and in Dapper/Edgy to, the hardware is the same.... I'm really sad about that

Revision history for this message
OberonKing (oberonking) wrote :
Revision history for this message
OberonKing (oberonking) wrote :
Revision history for this message
OberonKing (oberonking) wrote :

Here's k3b.log..... please somebody fix this please

Revision history for this message
Dave (brother-sand) wrote :

Similar problem here.

$ growisofs -dvd-compat -Z /dev/hdb=/home/me/iso/not-a-copyrighted-movie.iso

:-( "/dev/hdb=/home/me/iso/not-a-copyrighted-movie.iso": unexpected errno: No such file or directory

##
At this point you will just have to trust me that this file is present. The command worked fine under Ubuntu 7.10 , but fails under 8.04. I can still boot into my Debian partition to make the dvd with that command.

D.

Revision history for this message
rubadubdub (rvdmeijden+launchpad-deactivatedaccount-deactivatedaccount) wrote :

I have had the same problem. It had something to do with the wron UDMA mode for the DVD writer. Which has something to do with sata drivers taking over all ide en sata devices in Hardy.

All the problems I was having I wrote in the following tread:

http://ubuntuforums.org/showthread.php?t=767278

The solution for me was to edit the boot grub and ad the following to the end of the kernel line:
all_generic_ide

Like this:
kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=4fd2a7c6-a5b9-49c0-9488-88fbf7fa0983 ro quiet splash all_generic_ide

After a reboot this fixed everything for me.

I am still very interested to find out what exactly the is with the drivers, so If somebody knows please let me know.

R.

Changed in brasero:
status: New → Invalid
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

After adding all_generic_ide to the kernel line, it still happens for me.

Revision history for this message
Shlepzig (sam-blanchard) wrote :

I have been experiencing same or similar problems since the last patch to growisofs was released (both Hardy and Gutsy):

https://bugs.launchpad.net/debian/+source/dvd+rw-tools/+bug/162736

Prior the last set of patches I installed on May 1 using growsifs via k3b would still burn a iso but the resulting DVD was not consistently recognized by all applications (handbrake avidemux). Disks burned previous to the date of the growisofs patch are fully compliant.

Post the May 1st Patch installation DVDs burned from growisfs (via k3b) fail during burning, or are destroyed without reporting an error.

Shlepzig

ManOfSteel (anrabaro)
description: updated
Revision history for this message
Tom (tomasz-belina) wrote : Re: CD/DVD burning problem in hardy SOLVED --- BURN AT 2X

all_generic_ide worked for me and I think I know why. It is DMA/66 80 pin tape issue. Without all_generic_ide option, on my PC, kernel uses pata_via driver. My recorder can work in UDMA/66 mode and pata_via driver sets this mode for it. But my dvdrecorder is connected to mainbord by old 40 pin tape and it leads to transmission errors between mainboard and recorder. all_generic_ide kernel option turns on ata_generic driver and this driver set UDMA/33 mode for recoder which is best possible one because of tape limitation. I suspect that it is possible to discover tape kind (40 or 80 pin) on driver level and ata_generic driver makes it better then pata_via driver.

This is part of dmesg log without all_generic_ide kernel option:
[ 34.026040] scsi0 : pata_via
[ 34.027306] scsi1 : pata_via
[ 34.029150] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
[ 34.029154] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
[ 34.200604] ata1.00: ATA-7: Maxtor 6B160P0, BAH41B70, max UDMA/133
[ 34.200610] ata1.00: 320173056 sectors, multi 16: LBA48
[ 34.210922] ata1.01: HPA unlocked: 156250000 -> 156301488, native 156301488
[ 34.210932] ata1.01: ATA-5: WDC WD800BB-75CAA0, 16.06V16, max UDMA/100
[ 34.210936] ata1.01: 156301488 sectors, multi 16: LBA
[ 34.228375] ata1.00: configured for UDMA/133
[ 34.243861] ata1.01: configured for UDMA/100
[ 34.562591] ata2.00: ATAPI: Optiarc DVD RW AD-7173A, 1-01, max UDMA/66
[ 34.734281] ata2.00: configured for UDMA/66 <--------------

and this is the same part of dmes log with all_generic_ide option

[ 26.430082] scsi0 : ata_generic
[ 26.430171] scsi1 : ata_generic
[ 26.432019] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
[ 26.432023] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
[ 26.605110] ata1.00: ATA-7: Maxtor 6B160P0, BAH41B70, max UDMA/133
[ 26.605115] ata1.00: 320173056 sectors, multi 16: LBA48
[ 26.615511] ata1.01: HPA unlocked: 156250000 -> 156301488, native 156301488
[ 26.615516] ata1.01: ATA-5: WDC WD800BB-75CAA0, 16.06V16, max UDMA/100
[ 26.615520] ata1.01: 156301488 sectors, multi 16: LBA
[ 26.615534] ata1.00: configured for UDMA/133
[ 26.615536] ata1.01: configured for UDMA/100
[ 26.935225] ata2.00: ATAPI: Optiarc DVD RW AD-7173A, 1-01, max UDMA/66
[ 26.935238] ata2.00: configured for UDMA/33 <--------------

The best workaround for this issue would to be to force somehow pata_via driver to set UDMA/33 mode for recorder or just to buy new 80 pin tape :)

Revision history for this message
Chris O'Halloran (fattybones) wrote :

After upgrading to hardy, I can no longer burn CD's or DVD's. The only available speed is 2x and it does not work still. I am going to go back to gutsy I believe.

1 comments hidden view all 108 comments
Revision history for this message
Arnaud Dessein (arnaud.dessein) wrote :

Same problem here. I have a Sony VGN-C1S laptop with a Pionner DVR-416M CD/DVD recorder. I can no longer burn CD's or DVD's with neither brasero nor nautilus-cd-burner...

Here is a log file from brasero

I hope a fix will be released soon (and happy to know the problem doesn't come from my CD's).

Good luck and thank you...

Revision history for this message
rster (smythrr) wrote :

This still an issue.

I have spent weeks trying to burn a data DVD on Hardy. I have read every post possible. Every thread doesn't seem to come to a solution. I have an LG GSA-4040B DVD burner. I was half way through a spindle of Sony DVD and upgraded to Hardy from Gutsy.

- Did a fresh install of Hardy
- Update the firmware on the DVD drive
- Tried multiple brands of blank media
- Changed my IDE cable to the DVD drive from 40 pin to 80 pin.
- Set the drive to master/slave
- Tried the latest version of dvd+rw tools
- Tried mutliple dvd burning tools. Brasero, Nautilus, K3B, command line... All fail at burning a data DVD.
- Tried multiple kernel options, like "combined_mode=libata atapi_enabled=1" and "all_generic_ide"
- Tried enabling burnproof in nautilus.
- Tried burning at multiple speeds

So, with trying all this, I was left with a new set of multi colored coasters... A set of about 20.

However, I finally came to a solution last night. I reinstalled Gutsy, 7.10. After the install was complete, lone behold, I successfully burned a data DVD.

I have attached the K3B log.

Cheers

Revision history for this message
rster (smythrr) wrote :

Here is the dmesg report also.

Cheers

Revision history for this message
Cio (tuomo-aro) wrote :

This DVD burning issue should perhaps have higher importance status? Since upgrading to Hardy I encountered way more issues with burned DVDs but most of them still seemed to work at least with some DVD drive. In Windows XP, all of the DVDs burned with Hardy are totally unregognizable while all those burned with Gutsy work fine. If other users also have DVDs, which seem to work in Linux or in some old DVD player, they might not notice that the burns are still not valid.

This looks like a kernel or driver bug (I'm using x86_64 kernel with Athlon 64 CPU. It is not related to certain drive or media type. I'm using two very different decent quality burners and I've tried with both high quality DVD+R and DVD-R media and all combinations of those have quite identical issues (read error in the very same sector). I tested DVD recognition also with two very different Windows computers.

Burning with 2x speed is not a solution. It isn't even acceptable workaround for me as I'm used to burning with at least 16x speed. Please investigate if the issue concerns more HW than you assumed and consider raising the importance status of this bug.

Thanks

Revision history for this message
Dave (brother-sand) wrote :

This problem is resolved for me. I'm not entirely sure how it came about but it is reminiscent of the old SCSI representation issues I used to see in Debian. After a set of updates the device (previously at /dev/hdb ) failed entirely when trying to burn DVD or CD material. But when I put in a video DVD I noticed that the device now comes up as /dev/scd0 . I re-targeted my scripts to /dev/scd0 and everything works fine.

It used to be the case that you had to have SCSI emulation on a CD burner for cdrecord to work with it. This required a boot option in the lilo.conf like:
append="hdb=ide-scsi max_scsi_luns=1"

As of the 2.6 kernel this was no longer entirely necessary to burn a CD, but often cdrecord would still give you trouble unless you did the scsi emulation.

What's odd to me here is that I have no scsi emulation in my boot options, the ide-scsi module is not loaded, whereas the scsi_mod is, and this device, which I'm certain is hooked up to an IDE cable is showing up as /dev/scd0 . I personally made no changes, just did the updates and rebooted when the update manager said I needed to.

I'm pleased that the issue is resolved, but I'm a little disturbed that Linux, which I thought I understood well, has now become slightly more occult. I have an ide device showing up as scd0 and really no idea how it got that way.

I haven't looked at it under Debian, but I believe the device is still /dev/hdb under that system.

D.

Revision history for this message
Dave (brother-sand) wrote :

PS - I do not need to restrict my burning to 2X speed. Auto works fine and I've set it to 16X manually and everything is good.

D.

Revision history for this message
krahim (karim-rahim) wrote :

Please see the comments I posted to Bug #199040.

I have not been able to burn dvd's since the upgrade to hardy. I have two ubuntu machines both of which burned dvd's before the upgrade without any troubles.

With the 32 bit machine I can format, but even this fails with the 64.

karim@ubuntu01:~$ dvd+rw-format -force /dev/cdrw1
* BD/DVD±RW/-RAM format utility by <email address hidden>, version 7.0.
* 4.7GB DVD-RW media in Restricted Overwrite mode detected.
* formatting 63.5%
karim@ubuntu01:~$ growisofs -Z /dev/cdrw1 -J -R test.avi
Executing 'genisoimage -J -R test.avi | builtin_dd of=/dev/cdrw1 obs=32k seek=0'
I: -input-charset not specified, using utf-8 (detected in locale settings)
  2.78% done, estimate finish Sat May 31 16:27:14 2008
  5.56% done, estimate finish Sat May 31 16:26:56 2008
  8.32% done, estimate finish Sat May 31 16:27:02 2008
/dev/cdrw1: "Current Write Speed" is 6.1x1352KBps.
 11.10% done, estimate finish Sat May 31 16:27:59 2008
 13.87% done, estimate finish Sat May 31 16:27:50 2008
 16.65% done, estimate finish Sat May 31 16:27:44 2008
:-[ WRITE@LBA=37b0h failed with SK=4h/ASC=08h/ACQ=03h]: Input/output error
:-( write failed: Input/output error
/dev/cdrw1: flushing cache
/dev/cdrw1: writing lead-out

Note that after mucking with the system, the dvd mounted as /dev/cdrom instead of /dev/cdrom1 and then I was able to burn dvd rws. I noted what I think I did (basically I tried rollbacks) under bug #199040, but currently it mounts as cdrom1 and fails.

I wonder if burning dvd's is low priority?

Karim

rster (smythrr)
Changed in linux:
status: Triaged → Incomplete
Revision history for this message
Andy (andy-xillean) wrote :

I am having the similar issues
A little history.
This system was running Gutsy
I backed up /home on Gutsy by burning to DVD on this system
reformatted installed Hardy from cdrom with the DVD drive
currently in the system. After a fresh install of Hardy the problems
began.
What I am experiencing on 5 PCs 2 laptops is this.
Data CDs and music CDs work fine.
Data DVDs or movie DVDs or blank DVDs do not
work on this system since Hardy was installed.

More info:-

No errors in kern.log or dmesg

====================================
~$ mount /dev/dvd
mount: No medium found

DVDrw info
sudo hdparm -i /dev/dvd

/dev/dvd:

 Model=OPTORITEDVD RW DD1205 , FwRev=100e , SerialNo=
 Config={ Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=1024kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:383,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4
 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 *udma2
 AdvancedPM=no

 * signifies the current active mode
==============================
~$uname -a
Linux ubuntu 2.6.24-19-generic #1 SMP Wed Jun 4 16:35:01 UTC 2008 i686 GNU/Linux

===================

i have attached a lshal.txt file burned on this system right before I
wiped Gutsy and installed Hardy. fresh install.

Revision history for this message
Sebastien Bacher (seb128) wrote :

would be interesting to attach the same log taken on hardy

Revision history for this message
Andy (andy-xillean) wrote :

all the logs i have attached are taken from hardy. It had a DVD that was burned in gutsy that would not mount in hardy. That was the dvd that was in the drive when I did lshal command in Hardy.

Revision history for this message
Cio (tuomo-aro) wrote :

The compatibility issue with Windows XP (my comment 2008-05-30) seems to be related to DVD authoring, not to burning. I use dvdauthor and growisofs to burn DVDs and they seem to produce Windows XP incompatible DVDs since upgrade to Hardy. I tried making an ISO image using mkisofs and then burned it using Gutsy kernel and again using Windows XP. The result was a DVD, which isn't recognized as DVD in Windows XP and therefore cannot be played using Windows Media Player. Even if DVD burning seems to work better now in Hardy (kernel 2.6.24-19), I find it unuseful while the results have major compatibility issue.

Revision history for this message
Arnaud Dessein (arnaud.dessein) wrote :

Hi !

Could someone explain me why the importance of this bug is set to LOW ? I mean, I am pretty sure there is a lot important bugs related to security issues and so on, but I can not burn any CD or DVD since I am on Hardy. It is very very difficult for me not being able to make backups or burn important CDs as rescue CD or ubuntu LiveCD.

I do not know how if the "importance" changes how the bug report is considered and treated, and I am sure you are doing as fast as you can, but maybe you could reconsider the importance of this bug.

Thanks a lot.

Revision history for this message
Sebastien Bacher (seb128) wrote :

changing the settings will not really make the bug fixed faster, there is thousand of bugs opened and a very small team to work on those, the issue might be an annoying one but it's not a security bug nor destroy user datas and seems to be specific to some hardware, it might be annoying to you who have one of those though but that doesn't make the bug a priority for the distribution

Revision history for this message
Andy (andy-xillean) wrote :

The reason why its LOW is because being able to burn optical media or read DVDs, or restore your backups
from a DVD in Ubuntu is NOT a priority. This is why this problem has existed for several months now and is still set to low. If you want to burn CDs and DVDs and restore your Backup from Data DVDs them maybe Ubuntu is not for you. Get a Mac or maybe even Windows Vista Basic. Maybe you may have better luck with a floppy drive if you must use removable media and Ubuntu Hardy on the same computer.

Revision history for this message
Andy (andy-xillean) wrote :

lshal.txt in debug mode inserting data dvd and blank dvd.

Revision history for this message
Andy (andy-xillean) wrote :

hal.log

Changed in nautilus-cd-burner:
importance: Undecided → Low
status: New → Incomplete
status: Incomplete → Invalid
28 comments hidden view all 108 comments
Revision history for this message
Andy (andy-xillean) wrote :

I cannot believe that this problem is six months old and it seems that its not important. I guess burning CDs and reading DVDs is simply not a priority. They say this problem doesn't affect much people so no need to prioritize this problem. They are about to release Intrepid with this same problem. That just goes to show how low priority this is. What is not funny is that in about 40% of the 400+ computers that I have installed Ubuntu Hardy on I see this problem. Those 40% of the 400+ computers I have reloaded with PCLinuxOS and the problem disappears. This is a HUGE problem and it seems some people don't grasp the magnitude of this issue. 6 Months no solution to a show stopping problem that affects about 40% of PC with Ubuntu Hardy installed. Its really sad really. This problem and the failure of Canonical to see the importance of it and to fix it for 6 whole months has put a bad taste in my mouth and the mouth of over 200 of my customers that run Ubuntu. Sorry to have to say it but the truth hurts.

I have setup a brand new DELL Precision T5400. Fresh install of Hardy I insert a blank CD i get nothing. No
warning. Nothing in dmesg no error. I go to computer in gnome and click on the drive and I get "UNABLE TO MOUNT LOCATION" "NO MEDIA IN THE DRIVE"

This is a BRAND NEW Dell workstation with sata.

In its current state Hardy is not worthy of being called and LTS let alone ready for the office if u cant even burn a CD /DVD. very sad indeed.

Revision history for this message
pliz (pliz) wrote :

I agree with Andy - the issue is just sad.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is not that easy, there is some ten thousand bugs open on launchpad and only a small team working on those, nobody is charging you any money and lot of people working there a people hacking on their free time to try to fix your issues, if you real need to get that fixed maybe you should consider contributing or buying a support contract?
I've several computers and none is having this issue, the number of duplicates also shows that some users get the issue but that seems far of the number you list there, anyway discussing the number is not really constructive and what is lacking there is manpower not something you rants will likely change

Revision history for this message
krahim (karim-rahim) wrote : Re: [Bug 200337] Re: CD/DVD burning problem in hardy

Perhaps Ubuntu needs a triage nurse. I suspect if the right developer
or group or group would fix this quickly.

I did manage to get it working with various roll backs months ago but
not consistently. I suspected that if the dvd mounted as crom it
worked fine but if it mounted as crom0 it did not. Anyone else help me
with this? I did try sym links but...

Karim

On Mon, Oct 6, 2008 at 2:33 PM, pliz <email address hidden> wrote:
> I agree with Andy - the issue is just sad.
>
> --
> CD/DVD burning problem in hardy
> https://bugs.launchpad.net/bugs/200337
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
krahim (karim-rahim) wrote :

Hey Sebastien,

I appreciate the effort you all put it and appreciate that the OS is free.

Thanks!
Karim

On Mon, Oct 6, 2008 at 4:33 PM, Sebastien Bacher <email address hidden> wrote:
> the issue is not that easy, there is some ten thousand bugs open on launchpad and only a small team working on those, nobody is charging you any money and lot of people working there a people hacking on their free time to try to fix your issues, if you real need to get that fixed maybe you should consider contributing or buying a support contract?
> I've several computers and none is having this issue, the number of duplicates also shows that some users get the issue but that seems far of the number you list there, anyway discussing the number is not really constructive and what is lacking there is manpower not something you rants will likely change
>
> --
> CD/DVD burning problem in hardy
> https://bugs.launchpad.net/bugs/200337
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
krahim (karim-rahim) wrote :

I believe the concern was with the bug being categorized as low
priority. Is it possible to up the priority?

Karim

On Mon, Oct 6, 2008 at 4:33 PM, Sebastien Bacher <email address hidden> wrote:
> the issue is not that easy, there is some ten thousand bugs open on launchpad and only a small team working on those, nobody is charging you any money and lot of people working there a people hacking on their free time to try to fix your issues, if you real need to get that fixed maybe you should consider contributing or buying a support contract?
> I've several computers and none is having this issue, the number of duplicates also shows that some users get the issue but that seems far of the number you list there, anyway discussing the number is not really constructive and what is lacking there is manpower not something you rants will likely change
>
> --
> CD/DVD burning problem in hardy
> https://bugs.launchpad.net/bugs/200337
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Marcel (marcel-vd-berg) wrote :

I had some burning problems in 8.04.
Since I'm testing 8.10 alpha6, I never had any problems.

Revision history for this message
Andy (andy-xillean) wrote :

The reason why there are so many duplicates is because this issue is not just related to burning.
Here is a simple run down.

In some configurations :-

Hardy 8.04 LTS will

1) Fail to recognize any DVDs DVD-r etc. and will only read CD-Roms no burning on either CD or DVD

or

2) Fail to recongize only CD-ROMs and Burn to CD-ROMs only. Not DVDs.

or

3) Fail to recognize DVDs but no blanks

or

4) fail to recognize DVD media burned in Gutsy. Yet WinXP sees the DVD and all previous versions of Ubuntu
sees the DVD

In all these cases it does not work in gnome/nautilus nor does it work mounting manually on the command line.
it simply fails to see the media "no media in drive" and nothing no errors in syslog or dmesg.

Revision history for this message
Andy (andy-xillean) wrote :

Also in some cases a different batch of the same media will be recognized intermittently.

Revision history for this message
rster (smythrr) wrote :

I can understand Andy's frustration. I went through the same aggravation several months back. This is the main reason I'm still using Gutsy. I can also understand Sebastien's point that there are limited resources and a ton of bugs to be fixed. All of the developers work goes much appreciated.

But... Realistically, optical media drives have been around for over a decade, maybe closer to two. I think the most disappointing thing is the priority level of this bug/bugs. I find it hard to believe that there are over ten thousand more 'important' issues than this. I would consider this issue the same priority if a bunch of video cards, hard drives, key boards or another major devices just stopped working on a LTS release.

What's the point of having a nice office suite if you can't back your work up on a CD? What's the sense of having firewire card support to import home video if you can't put it on a DVD? What's the point of importing photos from your camera if you can't put them on a CD to send to family in the next time zone? What's the point of pirating movies off the internet if you can't put them on them on a DVD? (Ok, the last one was a joke, but you see my point).

I definitely think this issue should not have a low/none-existent priority. I would like to upgrade from Gutsy as some point. On the other hand, I guess there's lots of other distros out there.

My 2 cents.

Revision history for this message
Alan Johnson (nilgiri) wrote :

Yes, the issues is definitely with priority, not man power.

Sebastian,

Please reconsider based on Andy's last two responses. If the concern is that there are too many duplicates, then they should be combined in to one bug report and surely that priority should be higher. There is some small difference between the packages in 7.10 and 8.04, somewhere between dvd+rw-tools and the kernel, that caused all this to break. Speaking as a developer myself, that is a pretty good starting point for fixing a bug. While it is well out side my knowledge domain, from the outside, it looks like a quick fix for some one who knows the system and process. At the risk of repeating others, I think the trick is just get it right people with an appropriate priority. Andy's reference to numbers are certainly relevant to selecting an appropriate priority.

On an etiquette note, while some of the posts have a tone of less that patient, I don't feel that "maybe you should consider contributing" is an appropriate response to the legitimate argument that has been made for an upgrade to the priority here. I'm sure you just meant "contributing code" specifically and that you understand that we are all contributing here, in this report, and I expect that most of us contribute in many ways beyond this. For example, Andy may be paid to manage 400+ machines, but that is still a significant contribution to the cause. You may be contributing more often and perhaps in a more meaningful way to this project, but it is not appropriate to assume that others are not doing the same or more elsewhere. Again, I'm sure you didn't mean it that way and meant well, but that wording can easily be taken the wrong way.

Anyway, I greatly appreciate your efforts as I have seen you working on many bugs. I am sure every one here feels the same. Please keep up the good work and please keep working with us to better understand the issue. Perhaps a link to the official definition of the priorities would be useful in that effort?

Andy,

Given your situation, perhaps a support contract would be a wise thing to consider as Sebastian suggested. I sure would not complain if you paid them to fix this problem for me. ;p Seriously though, I'm not sure how that works, but I would not pay a dime if they would not commit to fixing the issue. If they would take payment to increase this priority, I think that is a reasonable thing for both them and you to pursue given their business model and your needs. Alternately, just keep running 7.10 until this bug gets fixed. I hear you loud and clear on the LTS and "it worked fine before" points, and I agree whole heartedly. However, we must all do what we can with what we have. That's not to say we should give up the effort on this bug. Since we have this forum, that's one of the things we can do. =)

Revision history for this message
Andy (andy-xillean) wrote :

We all appreciate the work of Sebastien and Martin and all the others that oil in swamps with the bugs. Believe me if I knew how to code I would have fixed this and the other highly visible nuances in this LTS release. I also appreciate the words of the noble Alan J. I will pay right now to have this fixed right now. I am not sure if getting a support contract will fix this problem. 10000 bugs are a lot and I remember when MS was getting chastised and ridiculed for releasing Windows2K with 10000 bugs. I think they are just flooded in a torrent of bugs and not enough manpower and the 6mnth release cycle adds even more pressure to the mix. I think Mark will have to come up with a solution to this 10000 bug situation. I know none of us blames Sebastien or Martin or any one else that have been working on many bugs not just this one. I Think Canonical needs to start focusing more on quality control hire more devs to fix these 10000 bugs. I just can't understand why this is low priority for 6 months now.

Revision history for this message
OberonKing (oberonking) wrote :

Sorry about the delay to post....
I fixed my problems to burn cd/dvd in my IDE Asus Burner, only added "all_generic_ide" (without quotes) to the kernel line on Grub's menu.lts.

Now I can burn cd/dvd without problems.... hope you can fix this

Revision history for this message
Sebastien Bacher (seb128) wrote :

oh, so the discussion there seems to be due to the bug settings not being triaged correctly and not about everybody being too busy to work at the issue? I'll try to get somebody looking at the bug again and set appropriate settings there
concerning the comment about the number of duplicate, there is only one duplicate

Changed in dvd+rw-tools:
assignee: ubuntu-kernel-team → nobody
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Everyone,

I realize everyone is experiencing issues on Hardy, but Marcel had posted something interesting:

https://bugs.edge.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/200337/comments/75

"I had some burning problems in 8.04. Since I'm testing 8.10 alpha6, I never had any problems."

I'm curious if anyone else has been able to test the upcoming Intrepid Ibex 8.10 release. The Beta version of Intrepid was most recently released - http://www.ubuntu.com/testing/intrepid/beta . If anyone would be willing to test and confirm this is still an issue in Intrepid that would be great. @Wouter Stomp, I'd particularly be interested in hearing from you since you are the original bug reporter.

The main reason for testing Intrepid would be so that we know if 1) The bug is resolved and we can try to narrow down a fix to backport to Hardy or 2) The issue still exists for Intrepid in which case we should provide the developers the most uptodate debugging information. Thanks.

Changed in linux:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

Sorry I can't help anymore with this bug. I recently got a new pc and I don't have the old one anymore. I do still have the dvd drive here, if anybody wants it for testing, I could send it.

Revision history for this message
krahim (karim-rahim) wrote :

I wanted to mention that I had this problem after upgrading. I did not
do a fresh install.

I have been upgrading since edgy on this machine and dapper on the other.
As I mentioned earlier, I think it has to do with the way, location,
the dvd drive mounts.

Karim

On Wed, Oct 8, 2008 at 7:01 AM, Wouter Stomp <email address hidden> wrote:
> Sorry I can't help anymore with this bug. I recently got a new pc and I
> don't have the old one anymore. I do still have the dvd drive here, if
> anybody wants it for testing, I could send it.
>
> --
> CD/DVD burning problem in hardy
> https://bugs.launchpad.net/bugs/200337
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

@Wouter Stomp, thanks for the update.

@krahim, can you be a little more specific. You mention you experience this issue after upgrading. Upgrading to Hardy? Or upgrading to Intrepid?

Revision history for this message
pliz (pliz) wrote :

To Leann Ogasawara:

(some offtopic)
I booted into the Live CD of intrepid but the graphics would not start. I traced it down to the fact that my Wacom Graphire3 table was plugged in to USB. When the tablet is unplugged, X starts with no problem, but crashes almost immediately after I plug in the tablet. Logs say error due to conflict between mouse and the tablet.

I did not try the CD/DVD issue.

Revision history for this message
krahim (karim-rahim) wrote :

Hi,

I had Edgy, and I think I did two upgrades in a row to upgrade to
Hardy on my laptop. I basically don't burn cd/dvds there.

On my laptop, where I do burn dvd's/cd. I noticed the problem
immediately after upgrading to Hardy from Feisty. It is only after I
noticed the problem on my desktop that I tried the laptop where the
problem also existed.

I guess Intrepid the new one (still beta)?

Now with two Hardy systems, I cannot burn dvds or cdroms from the command line.

Karim

On Thu, Oct 9, 2008 at 12:23 PM, Leann Ogasawara <email address hidden> wrote:
> @Wouter Stomp, thanks for the update.
>
> @krahim, can you be a little more specific. You mention you experience
> this issue after upgrading. Upgrading to Hardy? Or upgrading to
> Intrepid?
>
> --
> CD/DVD burning problem in hardy
> https://bugs.launchpad.net/bugs/200337
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Joel Oliver (joelol75) wrote :

pliz wrote:
> To Leann Ogasawara:
>
> (some offtopic)
> I booted into the Live CD of intrepid but the graphics would not start. I traced it down to the fact that my Wacom Graphire3 table was plugged in to USB. When the tablet is unplugged, X starts with no problem, but crashes almost immediately after I plug in the tablet. Logs say error due to conflict between mouse and the tablet.
>
> I did not try the CD/DVD issue.
>
>
Not to jump in on this, since it doesn't much matter anymore... But I
had a problem with my DVD burner as well. The cause was the mountpoint
and a config file that was left over from the earlier version. All that
it took to fix it was to delete /etc/udev/rules.d/70-persistent-cd.rules
and reboot... Well actually I moved the file to my home directory just
in case I needed it... Seems this was causing the problem. It gets
regenerated on reboot.

So if you're having problems this might be worth a shot... Some bugs
come from changes between versions with old config files laying around.

Joel.

Revision history for this message
DaveAbrahams (boostpro) wrote :

For what it's worth, I'm still not able to burn dual-layer DVDs in Hardy even though I'm using a kernel from Intrepid.

uname -a gives:
Linux hydra 2.6.26-6-server #4 SMP Thu Aug 7 15:52:39 EDT 2008 x86_64 GNU/Linux

Furthermore, after a failure, my drive has now stopped detecting inserted media

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

@krahim, you mention you are still using Hardy which is a 2.6.24 based kernel and @DaveAbrahms, you mention you are using an older 2.6.26 Intrepid kernel. Can you guys please test the newer 2.6.27-7.12 kernel for Intrepid? You can verify the kernel version you are running by looking at the output of 'cat /proc/version_signature' . Also, the latest daily images should have this newer kernel -http://cdimage.ubuntu.com/daily-live/current/ . Thanks.

Revision history for this message
Sergio Ventura (sergioventura) wrote :

Some week ago I updated Nautilus and now I can't burn CDs also with Nautilus burner.
It is very sad that I have to load windows for burning a CD.

Revision history for this message
Masoris (masoris) wrote :

I have a same problem on intrepid :(
I always failed to burn a DVD on both brasero and nautilus.

Revision history for this message
vof (vinceofarrell) wrote :
Download full text (4.6 KiB)

I have a similar and probably related problem so I will describe it here and not create another bug in the hope it will help the devs pinpoint the causes.

I recently upgraded a server from dapper to hardy after which my DVD-R burning archive script starting failing.

The script for dapper ran overnight, used mkisofs and worked a treat. The script was designed for non-computer people - they would periodically put a blank DVD-R in the drive in the evening. The return code from mkisofs was detected by the script. If the mkisofs run succeeded (that is, a blank disk had been inserted the previous evening), the script ejected it ready to be removed and filed the next day. If it failed, the script presumed it was because no media had been loaded and failed quietly.

The script needed to be changed for hardy - mkisofs was replaced by growisofs. I overcame bug 233942 by replacing genisoimage 1.1.6-1ubuntu6 with genisoimage 1.1.6-1ubuntu3. However, there are clearly still some other problems with DVD burning on hardy. Here are some of the symptoms I see:

1. The growisofs/genisoimage relationship does not seem quite right. An eject command after the growisofs command appears to be executed before genisoimage terminates. Indeed it seems to execute almost before genisoimage starts. See my thread here:
http://ubuntuforums.org/showthread.php?t=963701

2. growisofs always seems to return zero.

3.. If I run the archive script manually after loading a blank DVD-R, it creates a legitimate burned disk which I can read successfully if removed from the drive at that point.

4. If the script is run via cron overnight, I believe the disk is OK just as the result from 2. above is. Here are the key parts of the log which is emailed to me:

Executing 'genisoimage -r -J -joliet-long -V othona311008 -ldots /home/core/My Documents /home/othona_backups | builtin_dd of=/dev/dvd obs=32k seek=0'
Warning: creating filesystem that does not conform to ISO-9660.
I: -input-charset not specified, using utf-8 (detected in locale settings)
Using BOOKI000.SBD for ./rr_moved/Bookings.sbd (Bookings.sbd)
Using HOSTI000.SBD for ./rr_moved/Hosting stuff.sbd (Hosting stuff.sbd)
Using ONGOI000.SBD for ./rr_moved/Ongoing stuff.sbd (Ongoing stuff.sbd)
.
<lots of progress messages snipped>
.
 99.15% done, estimate finish Fri Oct 31 03:39:11 2008
 99.48% done, estimate finish Fri Oct 31 03:39:11 2008
 99.81% done, estimate finish Fri Oct 31 03:39:10 2008
Total translation table size: 0
Total rockridge attributes bytes: 916985
Total directory bytes: 2508800
Path table size(bytes): 14310
Max brk space used 7bc000
1517890 extents written (2964 MB)
/dev/dvd: flushing cache
/dev/dvd: updating RMA
/dev/dvd: closing disc

However, if the disk is left in the drive and the script runs 24 hours later on the same disk, it appears to try to burn the disk again (and I think it partially succeeds - see below) but fails as follows:

Executing 'genisoimage -r -J -joliet-long -V othona011108 -ldots /home/core/My Documents /home/othona_backups | builtin_dd of=/dev/dvd obs=32k seek=0'
Warning: creating filesystem that does not conform to ISO-9660.
I: -input-charset not specified, using utf-8 (detected in loc...

Read more...

Revision history for this message
Arnaud Dessein (arnaud.dessein) wrote :

I have just tried Intrepid on a LiveUSB (http://liveusb.info/dotclear/index.php) as I can not burn the LiveCD on Hardy...

I have been able to burn an entire DVD+R DL using Brasero without any problem. I have md5sum-checked every files : none of them is corrupted.

Maybe I have found my solution... Do you know why it does work on Intrepid for me ? Have some important things related to burning been updated/improved in Intrepid ?

Revision history for this message
krahim (karim-rahim) wrote :

Leann Ogasawara,

Can you first explain why you think this will work, or perhaps you
give a link answering the question. I suspect this is an issue with
the software package dvd+rw-tools, likely after an upgrade, as opposed
to a clean install.

Karim

On Mon, Oct 20, 2008 at 4:30 PM, Leann Ogasawara <email address hidden> wrote:
> @krahim, you mention you are still using Hardy which is a 2.6.24 based
> kernel and @DaveAbrahms, you mention you are using an older 2.6.26
> Intrepid kernel. Can you guys please test the newer 2.6.27-7.12 kernel
> for Intrepid? You can verify the kernel version you are running by
> looking at the output of 'cat /proc/version_signature' . Also, the
> latest daily images should have this newer kernel
> -http://cdimage.ubuntu.com/daily-live/current/ . Thanks.
>
> --
> CD/DVD burning problem in hardy
> https://bugs.launchpad.net/bugs/200337
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi krahim,

I had noticed in a previous dmesg output you had posted that it contained the following messages:

[12348.882839] UDF-fs: Partition marked readonly; forcing readonly mount
[12348.925801] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'Vista_PiterPenEdition_X86', timestamp 2007/02/12 06:13 (1f10)
[12398.732282] UDF-fs: Partition marked readonly; forcing readonly mount
[12398.777111] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'DVDVOLUME', timestamp 2007/01/06 15:42 (1f10)
[12464.590105] cdrom: This disc doesn't have any tracks I recognize!
[12464.604661] end_request: I/O error, dev sr0, sector 0
[12464.604673] Buffer I/O error on device sr0, logical block 0
[12464.604678] Buffer I/O error on device sr0, logical block 1
[12464.604681] Buffer I/O error on device sr0, logical block 2
[12464.604684] Buffer I/O error on device sr0, logical block 3
[12464.609607] end_request: I/O error, dev sr0, sector 0
[12464.609619] Buffer I/O error on device sr0, logical block 0
[12464.624309] end_request: I/O error, dev sr0, sector 0
[12464.624321] Buffer I/O error on device sr0, logical block 0
[12464.627196] end_request: I/O error, dev sr0, sector 0
[12464.627200] Buffer I/O error on device sr0, logical block 0
[12997.854714] cdrom: This disc doesn't have any tracks I recognize!

However that was from a 2.6.24 kernel. Intrepid, currently contains a much newer 2.6.27 kernel. So I'd be curious to see what the dmesg output is after you attempt to burn a DVD using the 2.6.27 kernel. Additionally, it would be great if you could post the exact commands you use to burn the DVD. You may be right that this is an issue with dvd+rw-tools for you. But I'd like to at least eliminate it possibly being a kernel issue. If you do feel it is an issue with dvd+rw-tools, it would be helpful to the dvd+rw-tools developers if you at least test the lastest version of dvd+rw-tools available in Intrepid. You also mentioned earlier that when you rolled back to an older version of dvd+rw-tools available you were able to burn DVD's? It would be good to specifically note the exact version of the package that worked and the current version that doesn't.

I unfortunately think that even though everyone may be experiencing the same symptom here, the root cause may be different bugs. Regardless, it would be great if those still experiencing issues with the most recent Intrepid release could provide appropriate debug logs and information. That includes package version information, steps to reproduce, debug output, dmesg output, etc. We can then at least focus on opening separate bug reports if necessary etc. Thanks.

Revision history for this message
pliz (pliz) wrote :

I have an interesting problem, which is related to CD/DVD but is not about burning. On my desktop aftr booting and working for a while I start seeing the following errors:

[ 710.020572] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 710.020588] ata1.00: BMDMA stat 0x24
[ 710.020602] ata1.00: cmd 35/00:10:0e:9b:ea/00:00:11:00:00/e0 tag 0 dma 8192 out
[ 710.020605] res 51/84:00:1d:9b:ea/84:00:11:00:00/e1 Emask 0x10 (ATA bus error)
[ 710.020612] ata1.00: status: { DRDY ERR }
[ 710.020618] ata1.00: error: { ICRC ABRT }
[ 710.020649] ata1: soft resetting link
[ 710.197482] ata1.00: configured for UDMA/133
[ 710.197513] ata1: EH complete
[ 710.198023] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
[ 710.198785] sd 0:0:0:0: [sda] Write Protect is off
[ 710.198795] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 710.199695] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

After a while I cannot use any CD o DVD media - they just not register anymore, although I can play DVD when just booted. My dmesg is flooded with messages of the above kind.

However, if I boot from USB (into intrepid, which is also on the hdd) then I never see this kind of messages.
I have 1 SATA disk and 1 ATA disk on a dedicated connection. I have a DVD reader and writer on the same connection.

So now I cannot even start testing CD/DVD burning since even reading does not work. Any ideas?

Revision history for this message
krahim (karim-rahim) wrote :
Download full text (3.1 KiB)

all right.

i have a couple silly questions...

is there a repository i have to add to up grade only the kernel? will
i have to hold back several packages?

i think i mixed repositories in the past, and had a file forcing versions...

karim

On Mon, Nov 10, 2008 at 9:38 PM, Leann Ogasawara <email address hidden> wrote:
> Hi krahim,
>
> I had noticed in a previous dmesg output you had posted that it
> contained the following messages:
>
> [12348.882839] UDF-fs: Partition marked readonly; forcing readonly mount
> [12348.925801] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'Vista_PiterPenEdition_X86', timestamp 2007/02/12 06:13 (1f10)
> [12398.732282] UDF-fs: Partition marked readonly; forcing readonly mount
> [12398.777111] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'DVDVOLUME', timestamp 2007/01/06 15:42 (1f10)
> [12464.590105] cdrom: This disc doesn't have any tracks I recognize!
> [12464.604661] end_request: I/O error, dev sr0, sector 0
> [12464.604673] Buffer I/O error on device sr0, logical block 0
> [12464.604678] Buffer I/O error on device sr0, logical block 1
> [12464.604681] Buffer I/O error on device sr0, logical block 2
> [12464.604684] Buffer I/O error on device sr0, logical block 3
> [12464.609607] end_request: I/O error, dev sr0, sector 0
> [12464.609619] Buffer I/O error on device sr0, logical block 0
> [12464.624309] end_request: I/O error, dev sr0, sector 0
> [12464.624321] Buffer I/O error on device sr0, logical block 0
> [12464.627196] end_request: I/O error, dev sr0, sector 0
> [12464.627200] Buffer I/O error on device sr0, logical block 0
> [12997.854714] cdrom: This disc doesn't have any tracks I recognize!
>
> However that was from a 2.6.24 kernel. Intrepid, currently contains a
> much newer 2.6.27 kernel. So I'd be curious to see what the dmesg
> output is after you attempt to burn a DVD using the 2.6.27 kernel.
> Additionally, it would be great if you could post the exact commands you
> use to burn the DVD. You may be right that this is an issue with dvd
> +rw-tools for you. But I'd like to at least eliminate it possibly being
> a kernel issue. If you do feel it is an issue with dvd+rw-tools, it
> would be helpful to the dvd+rw-tools developers if you at least test the
> lastest version of dvd+rw-tools available in Intrepid. You also
> mentioned earlier that when you rolled back to an older version of dvd
> +rw-tools available you were able to burn DVD's? It would be good to
> specifically note the exact version of the package that worked and the
> current version that doesn't.
>
> I unfortunately think that even though everyone may be experiencing the
> same symptom here, the root cause may be different bugs. Regardless, it
> would be great if those still experiencing issues with the most recent
> Intrepid release could provide appropriate debug logs and information.
> That includes package version information, steps to reproduce, debug
> output, dmesg output, etc. We can then at least focus on opening
> separate bug reports if necessary etc. Thanks.
>
> --
> CD/DVD burning problem in hardy
> https://bugs.launchpad.net/bugs/200337
> You received this bug notification because you are a direct sub...

Read more...

Revision history for this message
pliz (pliz) wrote :

I must apologize for my previous comments. In fact, my problem is always there. Does not matter what I boot from: HDD or USB. I have also installed a SATA PCI card (after getting a hint from some forum) and this does not help either. Now I am receiving the following:

[12359.200384] ata6: EH complete
[12390.692107] ata6.00: limiting speed to PIO0
[12390.692129] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[12390.692148] ata6.00: cmd a0/00:00:00:00:fc/00:00:00:00:00/a0 tag 0 pio 131072
 in
[12390.692157] cdb 28 00 00 02 1a 62 00 00 40 00 00 00 00 00 00 00
[12390.692165] res 58/00:02:00:00:f8/00:00:00:00:00/a0 Emask 0x6 (timeo
ut)
[12390.692180] ata6.00: status: { DRDY DRQ }
[12390.692212] ata6: soft resetting link
[12390.904451] ata6.00: configured for PIO0
[12390.904487] ata6: EH complete

Which is the same as previous. I am going to try switching to debian now and see if that changes the situation. However, I suspect it is a kernel issue.

Revision history for this message
pliz (pliz) wrote :

I have posted this into Bug#231575.Sorry for reposting it here, but it may be helpful for someone.

it looks like I found a solution. I did the following:

1. downloaded .config for the latest debian kernel (I guess 2.6.26)
2. downloaded the latest kernel (2.7.27.7) from kernel.org
3. compiled it the usual debian/ubuntu(make-kpkg) way using the downloaded .config (with minor almost random modifications)
4. bootted into the custom kernel.

Yesterday I have tested my system for 3-4 hours burning disks, doing cat
./* > /dev/null on several CDs and DVD disks for some manytimes just to
make sure.

I have not seen a single message of the kind reported above. It is close
to 24hours of constant work without these problems. Although I keep my
fingers crossed. If the solution is really working is there a way to
keep a standard debian kernel in my ubuntu sources. I just want all the
security patches and the stability of debian kernel :-)

May be that is a hint to ubuntu kernel team to check what they have
tweaked wrong?

Revision history for this message
Stefan Bader (smb) wrote :

Sorry about the long time without any response. I would like to get a picture about how this issue stand in
a) Hardy and
b) Jaunty
Is this still an issue with the latest kernels of both series (please consider to test Hardy-proposed as well if the current Hardy kernel in updates shows problems)?

Unfortunately there also seem to be several issues mixed into this. From possible application issues to kernel problems. Most of them sound as being problems with libata. So as stated by some reporters for Hardy "all_generic_ide" might be a solution. Since Intrepid there is a little more control over libata through libata.force, eg. to force 40cable conntections for decive ata1 one would specify "libata.force=1:40c".

Changed in linux (Ubuntu):
assignee: nobody → stefan-bader-canonical
Changed in k3b (Ubuntu):
status: New → Invalid
Revision history for this message
Stefan Bader (smb) wrote :

I am closing this as won't fix for now. There have been no usable comments for a long time. Also there have been so many issues mixed that it is near impossible to work with this report. If there are still issues like this I would propose to open a new one and try to keep different hardware separate.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
krahim (karim-rahim) wrote :

Sounds fair.

On Mon, Jul 27, 2009 at 8:24 AM, Stefan Bader<email address hidden> wrote:
> I am closing this as won't fix for now. There have been no usable
> comments for a long time. Also there have been so many issues mixed that
> it is near impossible to work with this report. If there are still
> issues like this I would propose to open a new one and try to keep
> different hardware separate.
>
> ** Changed in: linux (Ubuntu)
>       Status: Incomplete => Won't Fix
>
> --
> CD/DVD burning problem in hardy
> https://bugs.launchpad.net/bugs/200337
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
pliz (pliz) wrote :

So what should I do? I am still seeing the bug even in Karmic. My solution of taking .config from a stock Debian kernel and getting ubuntu kernel sources and recompiling with this configuration still works. If you tell me a step by step guide of providing you complete info needed o track the bug I am willing to do it. But it is same old thing: dmesg log full of
[ 595.704105] ata4: soft resetting link
[ 595.916356] ata4.00: configured for UDMA/44
[ 600.201554] ata4: EH complete
[ 629.005046] ata4.00: qc timeout (cmd 0xa0)
[ 629.005065] ata4.00: limiting speed to UDMA/33:PIO3
[ 629.005075] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 629.005097] ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 629.005100] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 629.005103] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
[ 629.005110] ata4.00: status: { DRDY ERR }
[ 629.005141] ata4: soft resetting link
[ 629.216359] ata4.00: configured for UDMA/33
[ 634.216054] ata4.00: qc timeout (cmd 0xa0)
[ 634.216067] ata4.00: TEST_UNIT_READY failed (err_mask=0x5)

CD/DVD ROM is nonexistent for the sysem - no disks are registered.

Revision history for this message
krahim (karim-rahim) wrote :

I do not see the bug on my system.
Karmic 64 bit. I do use kernel.org kernels.

Karim

On Fri, Nov 27, 2009 at 2:35 PM, pliz <email address hidden> wrote:
> So what should I do? I am still seeing the bug even in Karmic. My solution of taking .config from a stock Debian kernel and getting ubuntu kernel sources and recompiling with this configuration still works. If you tell me a step by step guide of providing you complete info needed o track the bug I am willing to do it. But it is same old thing: dmesg log full of
> [  595.704105] ata4: soft resetting link
> [  595.916356] ata4.00: configured for UDMA/44
> [  600.201554] ata4: EH complete
> [  629.005046] ata4.00: qc timeout (cmd 0xa0)
> [  629.005065] ata4.00: limiting speed to UDMA/33:PIO3
> [  629.005075] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> [  629.005097] ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> [  629.005100]          cdb 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> [  629.005103]          res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
> [  629.005110] ata4.00: status: { DRDY ERR }
> [  629.005141] ata4: soft resetting link
> [  629.216359] ata4.00: configured for UDMA/33
> [  634.216054] ata4.00: qc timeout (cmd 0xa0)
> [  634.216067] ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
>
> CD/DVD ROM is nonexistent for the sysem - no disks are registered.
>
> --
> CD/DVD burning problem in hardy
> https://bugs.launchpad.net/bugs/200337
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
pliz (pliz) wrote :

> I do use kernel.org kernels.

Yup! My point exactly: (1) ubuntu stock kernel bug, (2) custom kernels do not have it (3) it has been like that for ~2 years.
Custom kernels are not such a good idea: (1) effort to recompile each time kernel updates (a strong gentooish aftertaste), (2) lack of timely security updates.

Thanks for the effort.

Revision history for this message
Stefan Bader (smb) wrote :

Understood. The problem with this report was (iirc) that it
was sort of old and had a lot of different things mixed.
If you could just open a new bug with "ubuntu-bug linux",
then say in the description that the same (preferably Karmic)
kernel sources with just different configs show the problem
or not. Attach the config you used and subscribe me to that
bug. That would give a clean start.
Also with that kind of problems, it helps a lot to have a
detailed description of the physical layout of the drives on
the ata controller. How many drives on which port/controller.
Are they specially jumpered, how?
We had one case where a cdrom was jumpered slave, being the
only drive on one controller and the problem was solved just
by setting it to master.

Changed in gentoo:
status: Invalid → Unknown
Changed in gentoo:
importance: Unknown → Medium
Changed in dvd+rw-tools (Ubuntu):
status: Incomplete → Opinion
Displaying first 40 and last 40 comments. View all 108 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.