ATAPI CD-RW 52x + cdrecord error
I have Memorex CD-RW cds at up-to 4x multispeed. Burner is in topic, cdrecord version is 2.0 (default with slackware 9).
commad given: cdrecord -v speed=4 dev=0,0,0 -eject -data image.iso [return] To shorten your read, I will point out what I believe the source of the problem is.. Starting to write CD/DVD at speed 52 in real TAO mode for single session. I specified 4 and it goes at 52, which causes an overrun (or so I believe) anyone have any ideas why it doesn't work? error given: Cdrecord 2.0 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.25 Using libscg version 'schily-0.7' atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'ATAPI ' Identifikation : 'CD-RW 52XMax ' Revision : '140D' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO RAW/R96R Drive buf size : 1658880 = 1620 KB FIFO size : 4194304 = 4096 KB Track 01: data 615 MB Total size: 706 MB (70:00.34) = 315026 sectors Lout start: 706 MB (70:02/26) = 315026 sectors 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: 8 2T speed high: 0 (reserved val 10) power mult factor: 4 6 recommended erase/write power: 5 A1 values: 02 4C D0 A2 values: 4A D8 5A Disk type: Phase change Manuf. index: 40 Manufacturer: INFODISC Technology Co., Ltd. Blocks total: 359849 Blocks current: 359849 Blocks remaining: 44823 Starting to write CD/DVD at speed 52 in real TAO mode for single session. Last chance to quit, starting real write 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. BURN-Free is ON. Turning BURN-Free off Performing OPC... Starting new track at sector: 0 Track 01: 0 of 615 MB written.cdrecord: Input/output error. write_g1: scsi s endcmd: no error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03 00 00 Sense Key: 0x3 Medium Error, Segment 0 Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 5.643s timeout 40s write track data: error after 0 bytes Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 Writing time: 10.672s Average write speed 394.0x. Fixating... cdrecord: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 00 02 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 72 04 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x72 Qual 0x04 (empty or partially written reserved track) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.000s timeout 480s cmd finished after 0.000s timeout 480s Fixating time: 0.001s cdrecord: fifo had 64 puts and 1 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. -vexer |
cdrdao write --device 0,0,0 --speed 4 --driver generic-mmc-raw *.iso
This is if you actually have a device at 0,0,0. cdrecord -scanbus for actual. What a difference a binary makes.. |
yep, all the info above is correct and has been verified. So everything in the first post is a fact.
|
vexer@TheKeep:~/downloads/ISOs$ cdrdao write --device 0,0,0 --speed 4 --driver generic-mmc-raw openbsd-i386-3.3.iso
Cdrdao version 1.1.7 - (C) Andreas Mueller <andreas@daneb.de> SCSI interface library - (C) Joerg Schilling Paranoia DAE library - (C) Monty Check http://cdrdao.sourceforge.net/drives.html#dt for current driver tables. ERROR: openbsd-i386-3.3.iso:1: Illegal token: ERROR: openbsd-i386-3.3.iso:1: Illegal token: ERROR: openbsd-i386-3.3.iso:1: Illegal token: ERROR: openbsd-i386-3.3.iso:1: Illegal token: ERROR: openbsd-i386-3.3.iso:1: syntax error at "EOF" missing { TrackDef CdText } That is what I get with cdrdao, note that the first post error is cdrecord also, so 2 programs, 2 errors. |
Yep, so it still doesn't work. no matter how hard I try, (or often for that matter) I still get the same cdrecord error!
|
All times are GMT -5. The time now is 07:56 PM. |