[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Burning cd's



On Sunday 25 May 2003 14:25, Sridhar M.A. wrote:
>         mas@brahman:~/tmp$ cdrecord -dev=0,0,0 -speed=10 -dummy dasa1.img
>         Cdrecord 2.01a10 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg
> Schilling scsidev: '0,0,0'
>         scsibus: 0 target: 0 lun: 0
>         Linux sg driver version: 3.1.24
>         Using libscg version 'schily-0.7'
>         Device type    : Removable CD-ROM
>         Version        : 0
>         Response Format: 1
>         Vendor_info    : 'SAMSUNG '
>         Identifikation : 'CD-R/RW SW-248F '
>         Revision       : 'R604'
>         Device seems to be: Generic mmc CD-RW.
>         Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
>         Driver flags   : MMC-3 SWABAUDIO BURNFREE FORCESPEED
>         Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R
>         Starting to write CD/DVD at speed 10 in dummy TAO mode for single
> session. Last chance to quit, starting dummy write    0 seconds. Operation
> starts. cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB:
>  2A 00 00 03 B2 1B 00 00 1F 00
>         status: 0x2 (CHECK CONDITION)
>         Sense Bytes: F0 00 03 00 03 AF 87 0C 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 241543 (valid)
>         cmd finished after 0.787s timeout 40s
>         write track data: error after 496031744 bytes
>         cdrecord: Input/output error. flush cache: scsi sendcmd: no error
>         CDB:  35 00 00 00 00 00 00 00 00 00
>         status: 0x2 (CHECK CONDITION)
>         Sense Bytes: F0 00 03 00 03 AF 87 0C 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 241543 (valid)
>         cmd finished after 6.410s timeout 120s
>         Trouble flushing the cache

I had similar (though not exactly the same) problems. It seems it was due to 
the drive overheating, at lease it works since I installed the drive in a way 
that gave it more ventilation.

-- 
Got Backup?



Reply to: