unable to write ISO to CD-R

m4rtin · 07-26-2011, 05:11 AM

I tried to write debian-6.0.2.1-i386-netinst.iso to a CD-R(I tried few different CD-R disks), but ran into following error:

Code:

Track 01:   61 of  191 MB written (fifo 100%) [buf  87%]   7.9x.Errno: 5 (Input/output error)

Whole wodim output can be found here:

Code:

$ wodim -v dev=0,1,0 -sao debian-6.0.2.1-i386-netinst.iso
TOC Type: 1 = CD-ROM
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
scsidev: '0,1,0'
scsibus: 0 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.27
Wodim version: 1.1.11
SCSI buffer size: 64512
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'PHILIPS '
Identification : 'DVD+-RW SDVD8441'
Revision       : 'PH32'
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: 0x0014 (DVD-RW sequential recording) 
Profile: 0x0013 (DVD-RW restricted overwrite) 
Profile: 0x0011 (DVD-R sequential recording) 
Profile: 0x0010 (DVD-ROM) 
Profile: 0x000A (CD-RW) 
Profile: 0x0009 (CD-R) (current)
Profile: 0x0008 (CD-ROM) 
Profile: 0x0000 (Reserved/Unknown) 
Profile: 0x0000 (Reserved/Unknown) 
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/R16 RAW/R96R
Drive buf size : 1073152 = 1048 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
FIFO size      : 12582912 = 12288 KB
Track 01: data   191 MB        
Total size:      219 MB (21:43.89) = 97792 sectors
Lout start:      219 MB (21:45/67) = 97792 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: 262054
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...
Errno: 5 (Input/output error), read track info scsi sendcmd: no error
CDB:  52 01 00 00 00 FF 00 00 1C 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.001s timeout 240s
wodim: Cannot get next writable address for 'invisible' track.
wodim: This means that we are checking recorded media.
wodim: This media cannot be written in streaming mode anymore.
wodim: If you like to write to 'preformatted' RW media, try to blank the media first.
Writing pregap for track 1 at -150
Starting new track at sector: 0
Track 01:   61 of  191 MB written (fifo 100%) [buf  87%]   7.9x.Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB:  2A 00 00 00 7A 6D 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 0C 00 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 7.462s timeout 200s

write track data: error after 64186368 bytes
wodim: A write error occured.
wodim: Please properly read the error message above.
Writing  time:   72.422s
Average write speed  18.0x.
Min drive buffer fill was 87%
Fixating...
Fixating time:    0.004s
wodim: fifo had 1203 puts and 1012 gets.
wodim: fifo was 0 times empty and 734 times full, min fill was 95%.
$

Any ideas, what might cause this?

m4rtin · 07-26-2011, 08:58 AM

I tried with speed=1 as well, but it still wrote only first 61MB of data.

business_kid · 07-26-2011, 02:34 PM

85% is very low for a buffer. Is your memory good? I would stop cpu-intensive stuff, close the browser, ssh, don't play movies or sound, and try again. Also post the o/p of

hdparm -tT /dev/sda,
and the same for your cdrom

There is also some smartalec option which does everything except switch on the laser (i.e. ruin another cdrom). Fine tune with this.

man wodim

jefro · 07-26-2011, 04:59 PM

Maybe a better example. Use your full path and correct cd-drive.

# wodim -v -dao speed=4 dev=/dev/scd0 /root/projects/debian-500-i386-netinst.iso

teckk · 07-26-2011, 05:02 PM

If no luck with wodim then

Code:

cdrecord -scanbus

Check your drive

Code:

cdrecord -checkdrive dev=1,0,0

Burn

Code:

cdrecord -v dev=1,0,0 speed=8 -data debian-6.0.2.1-i386-netinst.iso

Or for a dry run

Code:

cdrecord -v dev=1,0,0 speed=8 -dummy -data debian-6.0.2.1-i386-netinst.iso

Or if you like

Code:

mkisofs -J -r -pad -graft-points debian-6.0.2.1-i386-netinst.iso | cdrecord dev=1,0,0 speed=8

man cdrecord
man mkisofs

m4rtin · 07-28-2011, 05:13 PM

business_kid, memory is fine and tested with Memtest86+. Why do you consider 87% full buffer very low? I mean it should introduce problems once the buffer is empty, shouldn't it?

How to ensure, that optical drive can read correctly? Make a image of some disk, which has 650MB of data on:

Code:

dd if=/dev/scd0 of=/home/martin/image.iso

..then make md5sum of the disk:

Code:

md5sum /dev/scd0

and finally compare this with:

Code:

md5sum /home/martin/image.iso

Or any better ideas?

afreitascs · 07-28-2011, 10:11 PM

The laser intensity is different in reading than in writing. I think ...

good luck

m4rtin · 07-29-2011, 02:35 AM

Quote:

Originally Posted by afreitascs

The laser intensity is different in reading than in writing. I think ...

good luck

Yes, the reading laser should be <5mW while writing laser is considerably more powerful. In addition, there is a Reed–Solomon error correction applied when reading from the disk as far as I know. On the other hand, the servomechanism which controls the lens distance from the disk and the servomechanism which controls the movement of the lens along the disk radius need to work correctly both in case of reading and writing. In addition, rotating motor needs to work properly both in case of reading and writing. I mean one can exclude quite many faults when reading from the disk works flawlessly

business_kid · 07-29-2011, 03:03 AM

I am of the opinion there's something awol or broken in the hardware setup. You have the man page and this is the time you should be reading it. To judge by the options, wodim is a cdrecord fork. Cdrecord is proof that nutty people can write software reasonably fit for purpose.

Try ldd /usr/bin/wodim |grep found - there should be _no_ output. Anything missing is mentioned, and install it.
Then, with a blank cd loaded, run

wodim -debug -dummy <your normal options> > file 2>&1

DO NOT paste it into this thread. Scour it yourself for stuff that it says is odd, or pastebin it. If you read the wodim man page, you will discover loads of options to make dodgy drives perform as hoped for, and you can start experimenting with these. It's your drive. Go for it. I found raw96r useful in one drive.