Cannot erase CD-RW with wodim after upgrading Ubuntu from 9.04 to 9.10
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cdrkit (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: wodim
When I want to erase a CD-RW with wodim 1.1.9 (under Ubuntu 9.10), I get an error message and the disk is not erased. The same command works fine in Ubuntu 9.04 before I upgraded Ubuntu to 9.10.
As Brasero and K3b also use wodim they also cannot erase CD-RWs anymore after upgrading to 9.10...
Below is the output of wodim under Ubuntu 9.10 and 9.04...
Thanks, Andreas
Edit: this seems to be a kernel issue: after downgrading the kernel to 2.6.28-10 (originally I had 2.6.31-17 under Ubuntu 9.10) I was able to erase CD-RWs. However, this can't be the solution to the problem as I don't want to use an old kernel. Also the problem apparently still exists with kernel 2.6.32-7
under Ubuntu 9.10:
andreas@ALIX:~$ /usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=4 -tao driveropts=burnfree blank=fast
TOC Type: 1 = CD-ROM
/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
devname: '/dev/sr0'
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 : 0
Response Format: 2
Capabilities :
Vendor_info : 'Optiarc '
Identification : 'DVD RW AD-7200A '
Revision : '1.06'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x000A (CD-RW)
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: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW) (current)
Profile: 0x0009 (CD-R)
Profile: 0x0008 (CD-ROM) (current)
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 SAO/R96R RAW/R96R
Drive buf size : 866304 = 846 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Reference speed: 2
Is not unrestricted
Is erasable
ATIP start of lead in: -11745 (97:25/30)
ATIP start of lead out: 359849 (79:59/74)
1T speed low: 0 (reserved val 0) 1T speed high: 4
2T speed low: 0 (reserved val 5) 2T speed high: 0 (reserved val 12)
power mult factor: 4 6
recommended erase/write power: 3
A1 values: 02 4C B0
A2 values: 5C D8 36
Disk type: Phase change
Manuf. index: 40
Manufacturer: INFODISC Technology Co., Ltd.
Speed set to 706 KB/s
Starting to write CD/DVD at speed 4.0 in real BLANK mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Performing OPC...
Blanking PMA, TOC, pregap
Errno: 5 (Input/output error), blank unit scsi sendcmd: no error
CDB: A1 01 00 00 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 9600s
/usr/bin/wodim: Cannot blank disk, aborting.
/usr/bin/wodim: Some drives do not support all blank types.
/usr/bin/wodim: Try again with wodim blank=all.
under Ubuntu 9.04:
andreas@ALIX:~$ /usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=4 -tao driveropts=burnfree blank=fast
TOC Type: 1 = CD-ROM
/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
devname: '/dev/sr0'
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 : 0
Response Format: 2
Capabilities :
Vendor_info : 'Optiarc '
Identification : 'DVD RW AD-7200A '
Revision : '1.06'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x000A (CD-RW)
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: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW) (current)
Profile: 0x0009 (CD-R)
Profile: 0x0008 (CD-ROM) (current)
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 SAO/R96R RAW/R96R
Drive buf size : 866304 = 846 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 5
Reference speed: 2
Is not unrestricted
Is erasable
ATIP start of lead in: -11745 (97:25/30)
ATIP start of lead out: 359849 (79:59/74)
1T speed low: 0 (reserved val 0) 1T speed high: 4
2T speed low: 0 (reserved val 5) 2T speed high: 0 (reserved val 12)
power mult factor: 4 6
recommended erase/write power: 3
A1 values: 02 4C B0
A2 values: 5C D8 36
Disk type: Phase change
Manuf. index: 40
Manufacturer: INFODISC Technology Co., Ltd.
Speed set to 706 KB/s
Starting to write CD/DVD at speed 4.0 in real BLANK mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Performing OPC...
Blanking PMA, TOC, pregap
Blanking time: 44.019s
| description: | updated |
| description: | updated |
| Schily (schilling-fokus) wrote | #1 |
| tags: | added: karmic regression-release |
You should send your bug report to the Linux kernel folks!
Note that this kernel bug has been reported many times during
the past few years.
When I did first see this Linux kernel bugs in 2004, the Linux kernel
folks did not show any interes in tying to fix it....
The bug seems to cause the SCSI command to be modified before
it finally was send to the drive. As a result, the drive complains with
an "illegal field in cdb" message.
These days, I am no longer able to reproduce the bug.
As you are able to repeoduce the bug, you should definitely report
the problem to the Linux kernel folks.