At face value, I'd guess you have a dirty lens.
On Fri, 2006-05-05 at 19:26 -0300, Matias Grana wrote:
hi!
I'm having serious problems with cdrecord (I actually use k3b, but it
calls cdrecord). Every once in a while it used not to finish recording
and exiting with errors. I lowered down the speed to 8x (the burner
reportedly can do a 52x) and this helped finishing burnings. But now I
wasted 2 cds in a row, with 8x speed. The end of the log is below. I
really don't know how to handle it. Any help?

Yours truly,
Matias

Log:

.... snip .....

Track 01:  187 of  701 MB written (fifo 100%) [buf  99%]   8.0x.
Track 01:  188 of  701 MB written (fifo 100%) [buf  99%]   8.2x.
/usr/bin/cdrecord: Success. write_g1: scsi sendcmd: no error
CDB:  2A 00 00 01 79 16 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 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.052s timeout 200s
/usr/bin/cdrecord: A write error occured.
/usr/bin/cdrecord: Please properly read the error message above.
write track data: error after 197701632 bytes
Writing  time:  190.103s
Average write speed  25.7x.
Min drive buffer fill was 94%
Fixating...
Fixating time:    1.636s
/usr/bin/cdrecord: fifo had 3242 puts and 3115 gets.
/usr/bin/cdrecord: fifo was 0 times empty and 2968 times full, min fill was 92%.

Reply via email to