Problem burning CD-ROM with cdrecord ... 5 blank CDs already broken

beachcoder · 2011-09-29 08:44:09

Hello there,

since a last update there seems to be a problem with the communication to my CD-burner. Tryring to burn a CD with k3b fails, now I tried directly with cdrecord, but it also fails. It is confusing: cdrecord seems to write data on the blank CDs because they can't be written or read anymore. Then all failes, and I don't want to test everything out now by always loosing more blank CDs.

Here some more information about my system:

$ cdrecord -scanbus
scsibus0:
        0,0,0     0) 'ATA     ' 'ExcelStor Techno' 'P22O' Disk
        0,1,0     1) *
        0,2,0     2) *
        0,3,0     3) *
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) *
        0,7,0     7) *
scsibus1:
        1,0,0   100) 'ATA     ' 'Hitachi HDP72505' 'GM4O' Disk
        1,1,0   101) *
        1,2,0   102) *
        1,3,0   103) *
        1,4,0   104) *
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *
scsibus4:
wodim: Warning: controller returns wrong size for CD capabilities page.
        4,0,0   400) 'TEAC    ' 'DW-552G         ' 'N4K1' Removable CD-ROM
        4,1,0   401) 'HL-DT-ST' 'DVDRAM GSA-4040B' 'A304' Removable CD-ROM
        4,2,0   402) *
        4,3,0   403) *
        4,4,0   404) *
        4,5,0   405) *
        4,6,0   406) *
        4,7,0   407) *

Device is

        4,1,0   401) 'HL-DT-ST' 'DVDRAM GSA-4040B' 'A304' Removable CD-ROM

So I did:

$ cdrecord -v -dao -dev=4,1,0 Various.iso
TOC Type: 1 = CD-ROM
scsidev: '4,1,0'
scsibus: 4 target: 1 lun: 0
WARNING: the deprecated pseudo SCSI syntax found as device specification.
Support for that may cease in the future versions of wodim. For now,
the device will be mapped to a block device file where possible.
Run "wodim --devices" for details.
Linux sg driver version: 3.5.34
Wodim version: 1.1.11
SCSI buffer size: 64512
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'HL-DT-ST'
Identification : 'DVDRAM GSA-4040B'
Revision       : 'A304'
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: 0x0014 (DVD-RW sequential recording) 
Profile: 0x0013 (DVD-RW restricted overwrite) 
Profile: 0x001A (DVD+RW) 
Profile: 0x001B (DVD+R) 
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 : 1204224 = 1176 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
Drive DMA Speed: 11582 kB/s 65x CD 8x DVD
FIFO size      : 4194304 = 4096 KB
Track 01: data   699 MB        
Total size:      803 MB (79:36.58) = 358244 sectors
Lout start:      803 MB (79:38/44) = 358244 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type A, high Beta category (A+) (3)
  ATIP start of lead in:  -11634 (97:26/66)
  ATIP start of lead out: 359846 (79:59/71)
Disk type:    Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 1602
Speed set to 4234 KB/s
Starting to write CD/DVD at speed  24.0 in real SAO mode for single session.
Last chance to quit, starting real write in    0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Sending CUE sheet...
Writing pregap for track 1 at -150
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB:  2A 00 FF FF FF 6A 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 10 2A 00 00 80 30 05 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x30 Qual 0x05 (cannot write medium - incompatible format) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.003s timeout 200s
write track pad data: error after 0 bytes
BFree: 1176 K BSize: 1176 K
Starting new track at sector: 0
Track 01:    0 of  699 MB written.Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB:  2A 00 00 00 00 00 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 10 2A 00 00 80 30 05 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x30 Qual 0x05 (cannot write medium - incompatible format) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.003s timeout 200s
write track data: error after 0 bytes
wodim: A write error occured.
wodim: Please properly read the error message above.
Writing  time:   32.523s
Average write speed 147.1x.
Fixating...
Fixating time:    0.006s
wodim: fifo had 64 puts and 1 gets.
wodim: fifo was 0 times empty and 0 times full, min fill was 100%.

k3b gave a message telling me to invoke k3bsetup, switching all devices on there didn't work. Also trying to run k3b as root did not help. Can anyone help?

So long,
beachcoder

andrej.podzimek · 2013-07-11 12:43:42

I'm facing exactly the same problem now. Initially I reported it as a K3b bug. https://bugs.archlinux.org/task/35858 However, it seems that running cdrecord manually also spoils blank CDs. All the data is written, even the checksumming succeeds (!!!) but then the CD looks blank when re-inserted.

The only difference with respect to your report: The CDs *can* be written multiple times. Obviously, this destroys them completely, so K3b's checksums won't match any more. (Actually they can't be even generated, because the CD is not readable any more.)

This is either a hardware failure, or some software glitch, such as a forgotten finalization step that would make the filesystem on the CD accessible. (Anyway, writing an ISO image should be just straightforward, no filesystem metadata is generated. Everything should be in the ISO file already, byte by byte.)

Last edited by andrej.podzimek (2013-07-11 12:45:34)

t0m5k1 · 2013-07-11 14:03:05

no necro bumping!

https://wiki.archlinux.org/index.php/Fo … Bumping.22

Arch Linux

#1 2011-09-29 08:44:09

Problem burning CD-ROM with cdrecord ... 5 blank CDs already broken

#2 2013-07-11 12:43:42

Re: Problem burning CD-ROM with cdrecord ... 5 blank CDs already broken

#3 2013-07-11 14:03:05

Re: Problem burning CD-ROM with cdrecord ... 5 blank CDs already broken

Board footer