Joerg Schilling wrote:
Bill Davidsen <davidsen@tmr.com> wrote:I'd like to think this was a media error, but the "no error" seems to^^^^^^^^^^^^^^^^^^^^^^^^RTFM man cdrecord to understand what this means.indicate otherwise. This is a regular backup, I do one of my working home firectories, then some other stuff in other sessions. The data for this burn is <300MB, and worked with another CD of the same brand.
Man page seems to say exactly what I expected, the kernel didn't reject the command because it was illegal or couldn't transfer it to the drive. That lets out a raft of things like having the drivers loaded in the wrong order and such.
iccarus:root> addir -ZG -f20 BILL=/home/bill + mkisofs -q -dDRNL -pad -graft-points BILL=/home/bill + cdrecord dev=0,0,0 -waiti -multi -eject fs=20m - Warning: creating filesystem that does not conform to ISO-9660. Cdrecord-Clone 2.01a19 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg SchillingA bit old.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 : 'AOPEN ' Identifikation : 'CD-RW CRW2040 ' Revision : '1.01' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).Driver flags : MMC SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96Rcdrecord: WARNING: Total disk size unknown. Data may not fit on disk. Starting to write CD/DVD at speed 16 in real TAO mode for multi session. Last chance to quit, starting real write 0 seconds. Operation starts. Turning BURN-Free off cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 00 4B 71 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: F1 00 05 00 00 4B 74 0C 00 00 00 00 10 02 00 00 Sense Key: 0x5 Illegal Request, deferred error, Segment 0Sense Code: 0x10 Qual 0x02 (id crc or ecc error) [No matching qualifier] Fru 0x0Sense flags: Blk 19316 (valid) cmd finished after 0.000s timeout 40swrite track data: error after 39553024 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above.It is obviously a problem inside your drive.
That's helpful, I was worried that I got a CD burning error in my keyboard or left speaker.
I suppose the chances of getting more information on what actually happened are small, an ecc error on a write is non-obvious to me, since I would expect that to be calculated in the drive and not visible to the CPU.
-- bill davidsen <davidsen@tmr.com> CTO TMR Associates, Inc Doing interesting things with small computers since 1979