karmic: brasero error on burning iso images

Bug #451350 reported by havhest on 2009-10-14
60
This bug affects 13 people
Affects Status Importance Assigned to Milestone
cdrkit (Ubuntu)
Low
Ubuntu Desktop Bugs
Nominated for Karmic by LeoRochael
Nominated for Lucid by LeoRochael

Bug Description

Binary package hint: brasero

I have one cd drive only. When trying to copy a cd, I create an iso image and burn this afterwards. Now, after having replaced the cd to copy with an empty cd, I select the iso image to write and the empty cd to write to. Brasero gives this error:
Error while burning. The drive is busy.
The error did not appear in jaunty.

release: Ubuntu karmic (development branch) 9.10
kernel: 2.6.31-13-generic #45-Ubuntu SMP Tue Oct 13 02:07:24 UTC 2009 x86_64 GNU/Linux
brasero version 2.28.1-0ubuntu1

ProblemType: Bug
Architecture: amd64
Date: Wed Oct 14 15:52:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
Package: brasero 2.28.1-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
SourcePackage: brasero
Uname: Linux 2.6.31-13-generic x86_64

havhest (sunnje-basedow) wrote :
Pedro Villavicencio (pedro) wrote :

could you get a brasero debug log? please run brasero as brasero --debug --brasero-media-debug &> brasero-debug.txt ; reproduce the bug and attach the resulting file to the report. thanks.

Changed in brasero (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete

Hi,
thanks for looking into this!
I couldn't run brasero --debug, the option seems not to exist, this is
what I get:
Please type brasero --help to see all available options
Looked in --help, but there was nothing about debug.

-----Original Message-----
From: <email address hidden> on behalf of Pedro Villavicencio
Sent: Wed 14-Oct-09 22:05
Subject: [Bug 451350] Re: karmic: brasero error on burning iso images

could you get a brasero debug log? please run brasero as brasero --debug
--brasero-media-debug &> brasero-debug.txt ; reproduce the bug and
attach the resulting file to the report. thanks.

** Changed in: brasero (Ubuntu)
   Importance: Undecided => Low

** Changed in: brasero (Ubuntu)
       Status: New => Incomplete

** Changed in: brasero (Ubuntu)
     Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)

--
karmic: brasero error on burning iso images
https://bugs.launchpad.net/bugs/451350
You received this bug notification because you are a direct subscriber
of the bug.

Status in "brasero" package in Ubuntu: Incomplete

Bug description:
Binary package hint: brasero

I have one cd drive only. When trying to copy a cd, I create an iso image
and burn this afterwards. Now, after having replaced the cd to copy with
an empty cd, I select the iso image to write and the empty cd to write to.
Brasero gives this error:
Error while burning. The drive is busy.
The error did not appear in jaunty.

release: Ubuntu karmic (development branch) 9.10
kernel: 2.6.31-13-generic #45-Ubuntu SMP Tue Oct 13 02:07:24 UTC 2009
x86_64 GNU/Linux
brasero version 2.28.1-0ubuntu1

ProblemType: Bug
Architecture: amd64
Date: Wed Oct 14 15:52:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
Package: brasero 2.28.1-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
SourcePackage: brasero
Uname: Linux 2.6.31-13-generic x86_64

Schily (schilling-fokus) wrote :

This could be a problem that is caused by "wodim". I recommend to use
the original software instead:

ftp://ftp.berlios.de/pub/cdrecord/alpha/

http://cdrecord.berlios.de/

affects: brasero (Ubuntu) → cdrkit (Ubuntu)
Changed in cdrkit (Ubuntu):
status: Incomplete → New
Greg Whiteley (greg-whiteley) wrote :

I get the same symptom and fiddling around with cdrecord I find that the options used for the burn are not compatible with the supported modes of the drive. The same error is reported in his attached brasero-session.log

> Excerpt from mine:
 Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R
> Excerpt from attached brasero-session.log
 Supported modes: TAO PACKET SAO

Taking the command reported in the attached brasero-session.log
$ wodim -v dev=/dev/sr0 speed=24 driveropts=burnfree -raw96r fs=16m -clone /home/user/brasero
...
 Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R
...
 wodim: Drive does not support RAW recording.
 wodim: Illegal write mode for this drive.

Removing -clone and -raw96r successfully writes _something_ to the disk, but its not a valid disk once its done. The -clone mode used on read requires -raw96r on write and its unsupported by these drives.

Adding in -sao (as suggested by my drives capabilities: SAO/R96R) returns:
 wodim: SAO RAW writing not yet implemented.

So possibilities occur (to unknowledgeable me):
1. wodim doesn't recognise that the drives support RAW any more (and did in Jaunty)
2. brasero has changed the way it reads and writes whole disks and this mode (-clone) isn't compatible with drives that don't support RAW (and the old way was)

I'll try to boot up in jaunty and see if wodim reports the same sets of supported modes

Some extra detail:
$ cdrecord -checkdrive -v
TOC Type: 1 = CD-ROM
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/cdrw
Using /dev/cdrom of unknown capabilities
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.9
Driveropts: 'burnfree'
SCSI buffer size: 64512
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'TEAC '
Identification : 'DVD+-RW DVW28SLC'
Revision : 'A.06'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009 (CD-R)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R)
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: 0x0012 (DVD-RAM)
Profile: 0x0002 (Removable disk)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW)
Profile: 0x0009 (CD-R) (current)
Profile: 0x0008 (CD-ROM)
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R
Drive buf size : 1267712 = 1238 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.

$ cdrecord --version
Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd
Wodim 1.1.9
Copyright (C) 2006 Cdrkit suite contributors
Based on works from Joerg Schilling, Copyright (C) 1995-2006, J. Schilling

Schily (schilling-fokus) wrote :

You are not using cdrecord but a defective fork from a very old version.

The fork was created by a hostile downstream who is missing the needed
skills for SCSI programming. The fork was given up on May 6th 2007.

There are more than 100 well known problems in the fork (most of them
did not exist in the original software) and there was never made an attempt
to fix these problems. None of the known problems exists in the original
software.

So far, I've not seen a drive that does support RAW writing, so you definitely
should try out the original software

BTW: It is always a good idea to check the original software.

ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de

Schily (schilling-fokus) wrote :

Sorry for the typo, it should read:

All drives I've seen did support RAW writing

havhest (sunnje-basedow) wrote :

Well, I installed brasero via apt-get, assuming the original software is installed.

Schily (schilling-fokus) wrote :

Unfortunately it is not. You need to get the original software yourself
from the location named above.

LeoRochael (leorochael) wrote :
Download full text (3.4 KiB)

I'm suffering from the same issue, on an 64bit Lenovo R500 with karmic.

Here is the output of "wodim -checkdrive -v"

TOC Type: 1 = CD-ROM
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/cdrw
Using /dev/cdrom of unknown capabilities
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.9
Driveropts: 'burnfree'
SCSI buffer size: 64512
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'MATSHITA'
Identification : 'DVD-RAM UJ880A '
Revision : 'SB01'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009 (CD-R)
Profile: 0x0012 (DVD-RAM)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R)
Profile: 0x001A (DVD+RW)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW)
Profile: 0x0009 (CD-R) (current)
Profile: 0x0008 (CD-ROM)
Profile: 0x0002 (Removable disk)
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO
Drive buf size : 1310720 = 1280 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.

For reference, here is the output of Schily's original cdrtools cdrecord output as well (in setuid mode):
$ cdrtools-2.01.01/cdrecord/OBJ/x86_64-linux-cc/cdrecord -version
Cdrecord-ProDVD-ProBD-Clone 2.01.01a74 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2010 J?rg Schilling

$ cdrtools-2.01.01/cdrecord/OBJ/x86_64-linux-cc/cdrecord -version
Cdrecord-ProDVD-ProBD-Clone 2.01.01a74 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2010 J�rg Schilling
leo@pelican:~/opt/cdrtools$ #cdrtools-2.01.01/cdrecord/OBJ/x86_64-linux-cc/cdrecord -checkdrive -v
leo@pelican:~/opt/cdrtools$
leo@pelican:~/opt/cdrtools$
leo@pelican:~/opt/cdrtools$
leo@pelican:~/opt/cdrtools$ cdrtools-2.01.01/cdrecord/OBJ/x86_64-linux-cc/cdrecord -checkdrive -v
Cdrecord-ProDVD-ProBD-Clone 2.01.01a74 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2010 J�rg Schilling
TOC Type: 1 = CD-ROM
Linux sg driver version: 3.5.34
Using libscg version 'schily-0.9'.
SCSI buffer size: 32768
No target specified, trying to find one...
Using dev=1,0,0.
atapi: 1
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'MATSHITA'
Identifikation : 'DVD-RAM UJ880A '
Revision : 'SB01'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: CD-R
Profile: DVD-RAM
Profile: DVD+R/DL
Profile: DVD+R
Profile: DVD+RW
Profile: DVD-R/DL layer jump recording
Profile: DVD-R/DL sequential recording
Profile: DVD-RW restricted overwrite
Profile: DVD-RW sequential recording
Profile: DVD-R sequential recording
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R (current)
Profile: CD-ROM
Profile: Removable Disk
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABA...

Read more...

LeoRochael (leorochael) wrote :
Download full text (3.3 KiB)

Notice that replacing the -raw96r with -sao makes both wodim and Schily's cdrecord work, but produces an unreadable disk with the following output on /var/log/messages:

eb 5 10:54:22 pelican kernel: [270552.215284] cdrom: This disc doesn't have any tracks I recognize!
Feb 5 10:54:22 pelican kernel: [270552.229721] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 5 10:54:22 pelican kernel: [270552.229734] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
Feb 5 10:54:22 pelican kernel: [270552.229745] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range
Feb 5 10:54:22 pelican kernel: [270552.229766] __ratelimit: 68 callbacks suppressed
Feb 5 10:54:22 pelican kernel: [270552.232812] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 5 10:54:22 pelican kernel: [270552.232824] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
Feb 5 10:54:22 pelican kernel: [270552.232835] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range
Feb 5 12:39:31 pelican kernel: [276861.213029] cdrom: This disc doesn't have any tracks I recognize!
Feb 5 12:39:31 pelican kernel: [276861.227610] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 5 12:39:31 pelican kernel: [276861.227623] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
Feb 5 12:39:31 pelican kernel: [276861.227635] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range
Feb 5 12:39:31 pelican kernel: [276861.231055] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 5 12:39:31 pelican kernel: [276861.231067] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
Feb 5 12:39:31 pelican kernel: [276861.231077] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range
Feb 5 13:44:45 pelican kernel: [280775.206188] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 5 13:44:45 pelican kernel: [280775.206200] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
Feb 5 13:44:45 pelican kernel: [280775.206211] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range
Feb 5 13:44:45 pelican kernel: [280775.211191] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 5 13:44:45 pelican kernel: [280775.211201] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
Feb 5 13:44:45 pelican kernel: [280775.211211] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range
Feb 5 13:44:45 pelican kernel: [280775.228078] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 5 13:44:45 pelican kernel: [280775.228090] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
Feb 5 13:44:45 pelican kernel: [280775.228101] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range
Feb 5 13:44:45 pelican kernel: [280775.231891] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 5 13:44:45 pelican kernel: [280775.231900] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
Feb 5 13:44:45 pelican kernel: [280775.231910] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range
Feb 5 13:44:45 pelican kernel: [280775.248075] cdrom: This disc doesn't have any trac...

Read more...

LeoRochael (leorochael) wrote :

Sorry, I meant to say "replacing -raw96r with -dao"

Brandon Snider (brandonsnider) wrote :

I packaged cdrtools so that it replaces Wodim and Genisoimage seamlessly, and it cleared up a similar bug I had related to burning DVD+RW discs. I have since burned some other types of discs without issue as well. If you want to give it a whirl, it's here:

https://launchpad.net/~brandonsnider/+archive/cdrtools/+packages

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers