1 |
At face value, I'd guess you have a dirty lens. |
2 |
On Fri, 2006-05-05 at 19:26 -0300, Matias Grana wrote: |
3 |
|
4 |
> hi! |
5 |
> I'm having serious problems with cdrecord (I actually use k3b, but it |
6 |
> calls cdrecord). Every once in a while it used not to finish recording |
7 |
> and exiting with errors. I lowered down the speed to 8x (the burner |
8 |
> reportedly can do a 52x) and this helped finishing burnings. But now I |
9 |
> wasted 2 cds in a row, with 8x speed. The end of the log is below. I |
10 |
> really don't know how to handle it. Any help? |
11 |
> |
12 |
> Yours truly, |
13 |
> Matias |
14 |
> |
15 |
> Log: |
16 |
> |
17 |
> .... snip ..... |
18 |
> |
19 |
> Track 01: 187 of 701 MB written (fifo 100%) [buf 99%] 8.0x. |
20 |
> Track 01: 188 of 701 MB written (fifo 100%) [buf 99%] 8.2x. |
21 |
> /usr/bin/cdrecord: Success. write_g1: scsi sendcmd: no error |
22 |
> CDB: 2A 00 00 01 79 16 00 00 1F 00 |
23 |
> status: 0x2 (CHECK CONDITION) |
24 |
> Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 08 03 00 00 |
25 |
> Sense Key: 0x4 Hardware Error, Segment 0 |
26 |
> Sense Code: 0x08 Qual 0x03 (logical unit communication crc error (ultra-dma/32)) Fru 0x0 |
27 |
> Sense flags: Blk 0 (not valid) |
28 |
> resid: 63488 |
29 |
> cmd finished after 0.052s timeout 200s |
30 |
> /usr/bin/cdrecord: A write error occured. |
31 |
> /usr/bin/cdrecord: Please properly read the error message above. |
32 |
> write track data: error after 197701632 bytes |
33 |
> Writing time: 190.103s |
34 |
> Average write speed 25.7x. |
35 |
> Min drive buffer fill was 94% |
36 |
> Fixating... |
37 |
> Fixating time: 1.636s |
38 |
> /usr/bin/cdrecord: fifo had 3242 puts and 3115 gets. |
39 |
> /usr/bin/cdrecord: fifo was 0 times empty and 2968 times full, min fill was 92%. |