Hi,

the initial error report of 2009 is probably due to a hardware problem
in the computers bus controller, or the cabling, or the drive's bus
controller.

> BraseroWodim stderr: CDB: 2A 00 00 01 6C 7E 00 00 1F 00
> ...
> BraseroWodim stderr: Sense Key: 0x0 No Additional Sense, Segment 11
> ...
> BraseroWodim stderr: Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 
> 00 00
> ...
> BraseroWodim stderr: Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0

wodim reported the error wrongly, because it does not recognize the error
message format, which is not supposed to be issued by a CD drive.

The error codes are rather: Key= 0xB, ASC= 0, ASCQ= 0.
This means "Command aborted". I.e. Linux decided to abort the WRITE
transaction to block 0x16C7E = 93310. No reason given. (Maybe in dmesg ?)

One can find several reports about this error message and its
misinterpretation by cdrecord, wodim, or growisofs.

Whatever, the error is neither the fault of Brasero nor of the burn program
wodim.

---------------------------------------------------------------------------

> https://ubuntuforums.org/showthread.php?p=7493563

The drive reports that it is not ready to write to block 0x256B = 9579.
That's a drive internal problem.

---------------------------------------------------------------------------

> https://ubuntuforums.org/showthread.php?t=1197582

This is simply a Medium Error, i.e. a problem between drive and medium.
No software on the Linux side of the cable is to blame.

---------------------------------------------------------------------------

> https://lists.ubuntu.com/archives/ubuntu-users/2009-April/179336.html

Totally unrelated.

---------------------------------------------------------------------------

> https://answers.launchpad.net/ubuntu/+source/brasero/+question/76444

The drive reports that it is not ready to write to block 0x1F9B = 8091.
About the same problem as in
  https://ubuntuforums.org/showthread.php?p=7493563

---------------------------------------------------------------------------

> BraseroCDRecord stderr: cdrecord: Input/output error. write_g1: scsi
sendcmd: no error

That's what cdrecord and wodim say when they get Key=0xB in the unexpected
error reply format.

---------------------------------------------------------------------------

> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/397412/comments/10
> 
> BraseroWodim stderr: Sense Key: 0x4 Hardware Error, deferred error, Segment 0
> ...
> BraseroWodim stderr: Sense Code: 0x09 Qual 0x00 (track following error) Fru 

This is a problem between drive and medium, reported in the expected
format.

---------------------------------------------------------------------------

> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/397412/comments/11/+download
> 
> BraseroCDRecord stderr: Sense Key: 0x5 Illegal Request, Segment 0
> ...
> BraseroCDRecord stderr: Sense Code: 0x30 Qual 0x05 (cannot write medium - 
> incompatible format) Fru 0x0

The drive did not like the mediumi state. Maybe it was already written.

---------------------------------------------------------------------------
Finally the report of today:

> https://launchpadlibrarian.net/331859195/brasero-session.log
> 
> BraseroCDRecord stderr: Sense Key: 0x3 Medium Error, Segment 0
> ...
> BraseroCDRecord stderr: Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0

The drive perceived an error when trying to write to the medium.
Block address was 0xFFFFFF6A = -150.
Strange as it is, -150 is the normal start address for a CD SAO run.
So no fault of the burn program.

---------------------------------------------------------------------------

So these bug reports are all about poorly working busses, drives, or media.
Not a single software bug in userland is to see.

Else i would advise to try the libburn backend of Brasero.
But in the cases reported here, success could only happen by incident
when the busses, drives, and media are in better mood.

Have a nice day :)

Thomas

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/397412

Title:
  brasero fails when burning DVD

Status in brasero package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: brasero wodim

  brasero 2.26.1 on ubuntu 9.04 jaunty, all updates applied as of July
  09, 2009.

  DVD ISO images, both DVD-Video and DVD-ROM images, fail to burn, data
  discs created in brasero also fail. A sample brasero log follows, in
  this instance the image was of a 4.1Gb DVD-Video. I have been living
  with this problem since upgrading from ubuntu 8.10 (in which brasero
  worked fine).

  I dual-boot with Windows XP and the same image writes ok using Nero on
  the same hardware, using media from the same spindle.

  ---brasero log start---
  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_PBU5WU.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
  BraseroWodim called brasero_job_get_action
  BraseroWodim getting varg
  BraseroWodim called brasero_job_get_action
  BraseroWodim got varg:
  BraseroWodim deactivating
  BraseroWodim called brasero_job_get_action
  BraseroWodim getting varg
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_get_device
  BraseroWodim called brasero_job_get_flags
  BraseroWodim called brasero_job_get_speed
  BraseroWodim called brasero_job_get_flags
  BraseroWodim called brasero_job_get_input_type
  BraseroWodim called brasero_job_get_fd_in
  BraseroWodim called brasero_job_get_current_track
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim got varg:
        wodim
        -v
        dev=/dev/sr0
        speed=8
        driveropts=burnfree
        -dao
        fs=16m
        -data
        -nopad
        /home/noel/Desktop/dvd.iso
  BraseroWodim Launching command
  BraseroWodim called brasero_job_get_fd_out
  BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot raise 
RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: devname: '/dev/sr0'
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: scsibus: -2 target: -2 lun: -2
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Linux sg driver version: 3.5.27
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Wodim version: 1.1.9
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: SCSI buffer size: 64512
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Beginning DMA speed test. Set CDR_NODMATEST environment 
variable if device
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: communication breaks or freezes immediately after that.
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stdout: TOC Type: 1 = CD-ROM
  BraseroWodim stdout: Driveropts: 'burnfree'
  BraseroWodim stdout: Device type    : Removable CD-ROM
  BraseroWodim stdout: Version        : 5
  BraseroWodim stdout: Response Format: 2
  BraseroWodim stdout: Capabilities   : 
  BraseroWodim stdout: Vendor_info    : 'PIONEER '
  BraseroWodim stdout: Identification : 'DVD-RW  DVR-217 '
  BraseroWodim stdout: Revision       : '1.05'
  BraseroWodim stdout: Device seems to be: Generic mmc2 DVD-R/DVD-RW.
  BraseroWodim stdout: Current: 0x0011 (DVD-R sequential recording)
  BraseroWodim stdout: Profile: 0x002B (DVD+R/DL) 
  BraseroWodim stdout: Profile: 0x001B (DVD+R) 
  BraseroWodim stdout: Profile: 0x001A (DVD+RW) 
  BraseroWodim stdout: Profile: 0x0016 (DVD-R/DL layer jump recording) 
  BraseroWodim stdout: Profile: 0x0015 (DVD-R/DL sequential recording) 
  BraseroWodim stdout: Profile: 0x0014 (DVD-RW sequential recording) 
  BraseroWodim stdout: Profile: 0x0013 (DVD-RW restricted overwrite) 
  BraseroWodim stdout: Profile: 0x0012 (DVD-RAM) 
  BraseroWodim stdout: Profile: 0x0002 (Removable disk) 
  BraseroWodim stdout: Profile: 0x0011 (DVD-R sequential recording) (current)
  BraseroWodim stdout: Profile: 0x0010 (DVD-ROM) 
  BraseroWodim stdout: Profile: 0x000A (CD-RW) 
  BraseroWodim stdout: Profile: 0x0009 (CD-R) 
  BraseroWodim stdout: Profile: 0x0008 (CD-ROM) 
  BraseroWodim stdout: Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
  BraseroWodim stdout: Driver flags   : SWABAUDIO BURNFREE 
  BraseroWodim stdout: Supported modes: PACKET SAO
  BraseroWodim stdout: Drive buf size : 1605632 = 1568 KB
  BraseroWodim stdout: FIFO size      : 16777216 = 16384 KB
  BraseroWodim stderr: Speed set to 11080 KB/s
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stdout: Track 01: data  4269 MB        
  BraseroWodim stdout: Total size:     4903 MB (485:47.12) = 2186034 sectors
  BraseroWodim stdout: Lout start:     4903 MB (485:49/09) = 2186034 sectors
  BraseroWodim stdout: Current Secsize: 2048
  BraseroWodim stdout: HINT: use dvd+rw-mediainfo from dvd+rw-tools for 
information extraction.
  BraseroWodim stdout: Blocks total: 2298496 Blocks current: 2298496 Blocks 
remaining: 112462
  BraseroWodim stdout: Starting to write CD/DVD at speed   8.0 in real SAO mode 
for single session.
  BraseroWodim stdout: Last chance to quit, starting real write in    4 
seconds.
  BraseroWodim called brasero_job_set_dangerous
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout:    3 seconds.
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout:    2 seconds.
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout: 
  BraseroWodim stdout:    1 seconds.   0 seconds. Operation starts.
  BraseroWodim stdout: Waiting for reader process to fill input buffer ... 
input buffer ready.
  BraseroWodim stdout: Performing OPC...
  BraseroWodim stdout: Sending CUE sheet...
  BraseroWodim called brasero_job_get_input_type
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: Starting new track at sector: 0
  BraseroWodim stdout: 
  BraseroWodim stdout: Track 01:    0 of 4269 MB written.
  BraseroWodim stdout: Track 01:    1 of 4269 MB written (fifo  98%) [buf  67%] 
 23.6x.
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: Track 01:    2 of 4269 MB written (fifo  99%) [buf  99%] 
  0.1x.
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: Track 01:    3 of 4269 MB written (fifo  99%) [buf  99%] 
  6.4x.
  .
  . (removed these redundant parts to save space)
  .
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: Track 01:  177 of 4269 MB written (fifo 100%) [buf  98%] 
  6.1x.
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: Track 01:  178 of 4269 MB written (fifo  99%) [buf  98%] 
  6.3x.
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: Track 01:  179 of 4269 MB written (fifo 100%) [buf  98%] 
  6.0x.
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: Track 01:  180 of 4269 MB written (fifo  99%) [buf  98%] 
  6.2x.
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: Track 01:  181 of 4269 MB written (fifo  99%) [buf  98%] 
  6.0x.
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stderr: Errno: 5 (Input/output error), write_g1 scsi sendcmd: no 
error
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: CDB:  2A 00 00 01 6C 7E 00 00 1F 00
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: status: 0x2 (CHECK CONDITION)
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 
00 00
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Sense Key: 0x0 No Additional Sense, Segment 11
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Sense flags: Blk 0 (not valid) 
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: cmd finished after 0.336s timeout 200s
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: wodim: A write error occured.
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: wodim: Please properly read the error message above.
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stdout: Track 01:  182 of 4269 MB written (fifo 100%) [buf  96%] 
  5.9x.
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: write track data: error after 191098880 bytes
  BraseroWodim stdout: Writing  time:   53.636s
  BraseroWodim stdout: Average write speed  73.8x.
  BraseroWodim stdout: Min drive buffer fill was 93%
  BraseroWodim stdout: Fixating...
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim stdout: Fixating time:    1.021s
  BraseroWodim stderr: wodim: fifo had 3265 puts and 3011 gets.
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: wodim: fifo was 0 times empty and 955 times full, min 
fill was 96%.
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stdout: HUP
  BraseroWodim stderr: HUP
  BraseroWodim process finished with status 254
  BraseroWodim called brasero_job_error
  BraseroWodim finished with an error
  BraseroWodim asked to stop because of an error
        error           = 0
        message = "no message"
  BraseroWodim stopping
  BraseroWodim got killed
  Session error : unknown (brasero_burn_record burn.c:2602)
  ---brasero log end---

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/brasero
  NonfreeKernelModules: nvidia
  Package: brasero 2.26.1-0ubuntu1
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: brasero
  Uname: Linux 2.6.28-13-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/397412/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to