[Bug 135283] image doesnt burn
benske
ben.beuster at gmail.com
Tue Aug 28 14:40:17 BST 2007
Public bug reported:
Binary package hint: k3b
System
-----------------------
K3b Version: 1.0
KDE Version: 3.5.6
QT Version: 3.3.7
Kernel: 2.6.20-16-generic
Devices
-----------------------
HL-DT-ST CD-ROM GCR-8523B 1.01 (/dev/hdd, ) [CD-ROM] [CD-ROM] [None]
HL-DT-ST DVDRAM GSA-H10N JL10 (/dev/hdc, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump]
Used versions
-----------------------
cdrecord: 1.1.2
cdrecord
-----------------------
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.2
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 1 = CD-ROM
Driveropts: 'burnfree'
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identification : 'DVDRAM GSA-H10N '
Revision : 'JL10'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009 (CD-R)
Profile: 0x0012 (DVD-RAM)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0015 (DVD-R/DL sequential recording)
Profile: 0x0016 (DVD-R/DL layer jump recording)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x001A (DVD+RW)
Profile: 0x001B (DVD+R)
Profile: 0x002B (DVD+R/DL)
Profile: 0x0010 (DVD-ROM)
Profile: 0x0009 (CD-R) (current)
Profile: 0x000A (CD-RW)
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 SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1053696 = 1029 KB
Drive DMA Speed: 14209 kB/s 80x CD 10x DVD
FIFO size : 12582912 = 12288 KB
Speed set to 4234 KB/s
Track 01: data 694 MB
Total size: 797 MB (79:02.53) = 355690 sectors
Lout start: 798 MB (79:04/40) = 355690 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 4
Is not unrestricted
Is not erasable
ATIP start of lead in: -11674 (97:26/26)
ATIP start of lead out: 359848 (79:59/73)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 23
Manufacturer: SKC Co., Ltd.
Blocks total: 359848 Blocks current: 359848 Blocks remaining: 4158
Starting to write CD/DVD at speed 24.0 in real TAO mode for single session.
Last chance to quit, starting real write in 2 seconds.
1 seconds.
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: 0 of 694 MB written.
Track 01: 1 of 694 MB written (fifo 99%) [buf 56%] 0.8x.
Track 01: 2 of 694 MB written (fifo 100%) [buf 99%] 25.8x.
Track 01: 3 of 694 MB written (fifo 100%) [buf 99%] 17.0x.
Errno: 0 (Success), write_g1 scsi sendcmd: no error
CDB: 2A 00 00 00 07 25 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 10 E3 92 8F 80 08 03 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x08 Qual 0x03 (logical unit communication crc error (ultra-dma/32)) Fru 0x0
Sense flags: Blk 0 (not valid)
resid: 63488
cmd finished after 0.026s timeout 40s
/usr/bin/wodim: A write error occured.
/usr/bin/wodim: Please properly read the error message above.
write track data: error after 3745792 bytes
Writing time: 17.054s
Average write speed 279.1x.
Min drive buffer fill was 56%
Fixating...
Fixating time: 20.056s
cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/hdc speed=24 -tao driveropts=burnfree -eject -data -tsize=355688s -
** Affects: k3b (Ubuntu)
Importance: Undecided
Status: New
--
image doesnt burn
https://bugs.launchpad.net/bugs/135283
You received this bug notification because you are a member of Ubuntu
Burning Team, which is a bug contact for k3b in ubuntu.
More information about the Ubuntu-burning
mailing list