input/output error causes cd burning to fail.

[mictremblay52]

Binary package hint: brasero

BraseroGrowisofs reports input/output error and exits with new cd burner. It is not limited to Brasero though. The problem exists with many burning applications, but did not exist with Gutsy.

ProblemType: Bug
Architecture: amd64
Date: Thu Sep 25 21:11:45 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 0.8.1-0ubuntu2~hardy1
PackageArchitecture: amd64
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: brasero
Uname: Linux 2.6.24-19-generic x86_64

[Mackenzie Morgan (maco.m)]

What error does Brasero give? When does it give it? What report are you talking about? What procedure? Please be more specific.

[mictremblay52 (michel-sylmic)]

Hi,

Here is the log for the message. The same program work well with UBUNTU
7.10.
I have this messge with UBUNTU 8.04 and for all the other program i
tried to use with my burner (new one).
Other program are : K3B, DVD95, Home user Backup, etc.

Michel Tremblay

Mackenzie Morgan a écrit :
> What error does Brasero give? When does it give it? What report are
> you talking about? What procedure? Please be more specific.
>
> ** Changed in: brasero (Ubuntu)
> Status: New => Incomplete
>
>

[Mackenzie Morgan (maco.m)]

When you tested and had it work with 7.10 was it the same burner? If not, could you test that? It says it was a write error, so I suspect it's a hardware issue.

[Mackenzie Morgan (maco.m)]

From reporter, emailed to me instead of to the bug:
I have 2 hard disk and 2 UBUNTU installed, one is 7.10 and is intalled on hda1 and the the second is 8.04 and is installed to hdb1.

Yes it's the same burner. I bought this new one because i suspect that it was a burner problem, but the problem is the same with the 2 devices the old and the new one.

I send back the new burner to the store where i bought this unit and asked for a test. They burned 1 cd and 3 dvd on a WINDOWS system without any problems. The day after i installed it on my whife PC and did a test to burn a cd and a dvd, it was working well also on WINDOWS.

So on 2 machines with 2 differents WINDOWS systems and on another machine (mine) with LINUX 7.10 it's work well without any errors.

The simptoms is, when the program start the burning process the burner start working for 30 seconds and then the program stop and gave me this error. If i look at the disk i saw some work on the disk for 1/5 of the surface.

[Mackenzie Morgan (maco.m)]

Can CDs be burned from the command line?

[Mackenzie Morgan (maco.m)]

sudo wodim -v dev=/dev/scd0 driveropts=burnfree thing.iso

Replace thing.iso with whatever disk image you want to try to burn.

[mictremblay52 (michel-sylmic)]

Hi,

Here are 2 logs for the problem one with UBUNTU 8.04 and the second with
UBUNTU 7.10 .

Michel

[mictremblay52 (michel-sylmic)]

Hi,

Here are the logs for the command you asked me to do.

I did one with UBUNTU 7.10 and one with UBUNTU 8.04.

root@michel-7-10:/home/michel# sudo wodim -v dev=/dev/hdc
driveropts=burnfree /home/michel/Vidéos/THE_CONTRACT.iso
wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
TOC Type: 1 = CD-ROM
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.6
Driveropts: 'burnfree'
SCSI buffer size: 64512
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVD-RAM GSA-H55N'
Revision : '1.03'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x001B (DVD+R)
Profile: 0x0012 (DVD-RAM)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R) (current)
Profile: 0x001A (DVD+RW)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW)
Profile: 0x0009 (CD-R)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Drive buf size : 1409024 = 1376 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
Drive DMA Speed: 92160 kB/s 523x CD 66x DVD
FIFO size : 12582912 = 12288 KB
Track 01: data 4330 MB
Total size: 4973 MB (492:43.38) = 2217254 sectors
Lout start: 4973 MB (492:45/29) = 2217254 sectors
Current Secsize: 2048
HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction.
Blocks total: 2295104 Blocks current: 2295104 Blocks remaining: 77850
Speed set to 16620 KB/s
Starting to write CD/DVD at speed 13.0 in real unknown mode for single
session.
Last chance to quit, starting real write i 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0
Track 01: 4330 of 4330 MB written (fifo 100%) [buf 91%] 12.6x.^[[3~
Track 01: Total bytes read/written: 4540936192/4540936192 (2217254 sectors).
Writing time: 360.224s
Average write speed 10.3x.
Min drive buffer fill was 0%
Total of 2259 possible drive buffer underruns predicted.
Fixating...
Fixating time: 14.548s
wodim: fifo had 71525 puts and 71525 gets.
wodim: fifo was 0 times empty and 9159 times full, min fill was 81%.
root@michel-7-10:/home/michel#

root@michel-western:/home/michel# sudo wodim -v dev=/dev/scd0
driveropts=burnfree /home/michel/Vidéos/STREET_KINGS.iso
wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
TOC Type: 1 = CD-ROM
scsidev: '/dev/scd0'
devname: '/dev/scd0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.6
Driveropts: 'burnfree'
SCSI buffer size: 64512
Device type : Removable CD-ROM...

[Dimitrios Symeonidis (azimout)]

reassigning to brasero for now, since wodim completed successfully...
By the way, brasero uses a new backend in Jaunty (9.04). Michel, could you please try with the latest version of Ubuntu and let us know if the issue persists?
Thank you, and good luck

[exzemat (exzemat)]

again
in jaunty 9.04

dvd-rw and kubuntu.iso

Checking session consistency (brasero_burn_check_session_consistency burn.c:1905)
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_set_output_size_for_current_track
BraseroBurnURI stopping
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_session_output_size
BraseroBurnURI output set (IMAGE) image = /tmp/brasero_tmp_HXCBTU.bin toc = none
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_current_track
BraseroBurnURI called brasero_job_get_input_type
BraseroBurnURI no burn:// URI found
BraseroBurnURI stopping
BraseroChecksumImage called brasero_job_get_current_track
BraseroChecksumImage called brasero_job_get_action
BraseroChecksumImage called brasero_job_get_flags
BraseroChecksumImage Dummy operation, skipping
BraseroChecksumImage called brasero_job_get_current_track
BraseroChecksumImage called brasero_job_get_action
BraseroChecksumImage called brasero_job_get_flags
BraseroChecksumImage Dummy operation, skipping
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs getting varg
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_get_input_type
BraseroGrowisofs got varg:
BraseroGrowisofs deactivating
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs getting varg
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_get_flags
BraseroGrowisofs called brasero_job_get_speed
BraseroGrowisofs called brasero_job_get_device
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_get_session_output_size
BraseroGrowisofs called brasero_job_get_input_type
BraseroGrowisofs called brasero_job_get_fd_in
BraseroGrowisofs called brasero_job_get_current_track
BraseroGrowisofs called brasero_job_set_current_action
BraseroGrowisofs got varg:
 growisofs
 -use-the-force-luke=notray
 -use-the-force-luke=dummy
 -use-the-force-luke=dao
 -use-the-force-luke=4gms
 -dvd-compat
 -speed=1
 -use-the-force-luke=tracksize:356254
 -use-the-force-luke=tty
 -Z
 /dev/sr0=/home/mat/Téléchargements/kubuntu-9.04-desktop-i386.iso
BraseroGrowisofs Launching command
BraseroGrowisofs called brasero_job_get_fd_out
BraseroGrowisofs stdout: Executing 'builtin_dd if=/home/mat/Téléchargements/kubuntu-9.04-desktop-i386.iso of=/dev/sr0 obs=32k seek=0'
BraseroGrowisofs called brasero_job_set_dangerous
BraseroGrowisofs stderr: /dev/sr0: engaging DVD-RW DAO upon user request...
BraseroGrowisofs stderr: /dev/sr0: reserving 356254 blocks
BraseroGrowisofs stderr: , warning for short DAO recording
BraseroGrowisofs stderr: /dev/sr0: "Current Write Speed" is 1.0x1352KBps.
BraseroGrowisofs stdout: 1572864/729608192 ( 0.2%) @0.0x, remaining 30:51 RBU 100.0% UBU 2.0%
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_set_current_action
BraseroGrowisofs stdout: 1572864/729608192 ( 0.2%) @0.0x, remaining 54:00 RBU 100.0% UBU 100.0%
BraseroGrowisofs called brasero_job_get_action
BraseroGrowisofs called brasero_job_set_current_action
BraseroGrowisofs stdout: 1572864/7296...

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Is this reproducible with Ubuntu 9.10 the Karmic Koala? Please test and provide us of feedback about it, Thanks in advance..

[exzemat (exzemat)]

-ubuntu Karmic (gnome)
-brasero 2.28.2

I tried successfully to burn kubuntu.iso on dvd-rw : no problem

I don't know if I just was lucky or if problems disappeared

thank you for your job

[Victor Vargas (kamus)]

According to the last comments this issue is working fine in latest releases of Brasero so for now I will mark this report as closed, but if you encounter that this issue reappears in Ubuntu Lucid/Maverick please reopened again. Thanks in advance.