[nflug] Problem burning CD's

Joe josephj at main.nc.us
Sun Mar 12 13:52:56 EST 2006


Joe wrote:
> I 'm writing a script that takes images of my partitions on my primary 
> drive (created by another script in 600MB chunks and stored on another 
> drive) and burns them to CDROMS.  This script burned 14 CDROMS.  I 
> then added code to check the md5sums to verify each CDROM.  I ran it 
> again (with cdrecord commented out) and it confirmed that 13 of the 14 
> CDROMS were good.  The only one that failed was a short one called 
> root004.  So I figured I had one bad CDROM and did that one again.  It 
> came up with the identical error on the new CDROM disk.  I also tried 
> a cmp of the two files and got the same error.
>
> It looks like everything ran fine (like it did for the other 13 
> images), but I can't even do an ls on it.  dmesg seems to show it has 
> big problems - like no directory (FAT, etc.) on it.
>
> Any ideas what might cause this to happen twice in a row - before I 
> make more coasters?
>
> This is a desktop single user system and I wasn't running anything 
> else when I was doing this (other things were in memory, but idle).  
> There were no power surges, etc. that I was aware of and the other 13 
> disks are fine.
>
> TIA
>
> Joe
>
> Inside loop of script to burn CDROM backups
>
>  echo
>  echo "Creating image to burn"
>  echo
>  mkisofs -J -r -o ${IMAGE}.iso ../$IMAGE
>  STATUS=$?
>  if [ "$STATUS" -ne 0 ]
>  then
>    echo "Could not create /mnt/portable/iso/${IMAGE}.iso"
>    mkisofs returned $STATUS
>    echo $SCRIPT aborted
>    exit 1
>  fi
>
>  echo
>  echo Burning image to CDROM
>  echo
>  cdrecord -v -speed=4 -data -dev=1,0,0 ${IMAGE}.iso
>  STATUS=$?
>  if [ "$STATUS" -ne 0 ]
>  then
>    echo "Could not burn /mnt/portable/iso/${IMAGE}.iso"
>    echo cdrecord returned $STATUS
>    echo $SCRIPT aborted
>    exit 1
>  fi
>
>  echo
>  echo Verifying Checksum of CDROM
>  echo
>  MSUM1=( `md5sum ../${IMAGE}` )
>  rm -f ${IMAGE}.iso
>  MSUM2=( `md5sum /mnt/cdrom/$IMAGE` )
>
>
> Output from script
>
> Creating image to burn
>
>  9.81% done, estimate finish Mon Mar  6 20:06:21 2006
> 19.62% done, estimate finish Mon Mar  6 20:06:26 2006
> 29.39% done, estimate finish Mon Mar  6 20:06:27 2006
> 39.20% done, estimate finish Mon Mar  6 20:06:28 2006
> 48.98% done, estimate finish Mon Mar  6 20:06:29 2006
> 58.79% done, estimate finish Mon Mar  6 20:06:29 2006
> 68.57% done, estimate finish Mon Mar  6 20:06:29 2006
> 78.37% done, estimate finish Mon Mar  6 20:06:31 2006
> 88.15% done, estimate finish Mon Mar  6 20:06:30 2006
> 97.96% done, estimate finish Mon Mar  6 20:06:30 2006
> Total translation table size: 0
> Total rockridge attributes bytes: 248
> Total directory bytes: 0
> Path table size(bytes): 10
> Max brk space used 6064
> 51056 extents written (99 Mb)
>
> Burning image to CDROM
>
> Cdrecord 2.0 (i586-mandrake-linux-gnu) Copyright (C) 1995-2002 Jörg 
> Schilling
> TOC Type: 1 = CD-ROM
> scsidev: '1,0,0'
> scsibus: 1 target: 0 lun: 0
> Linux sg driver version: 3.1.24
> Using libscg version 'schily-0.7'
> atapi: 1
> Device type    : Removable CD-ROM
> Version        : 0
> Response Format: 1
> Vendor_info    : 'LITE-ON '
> Identifikation : 'LTR-12101B      '
> Revision       : 'LS39'
> Device seems to be: Generic mmc CD-RW.
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> Driver flags   : MMC SWABAUDIO BURNFREE
> Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96P RAW/R96R
> Drive buf size : 1658880 = 1620 KB
> FIFO size      : 4194304 = 4096 KB
> Track 01: data    99 MB
> Total size:      114 MB (11:20.77) = 51058 sectors
> Lout start:      114 MB (11:22/58) = 51058 sectors
> Current Secsize: 2048
> ATIP info from disk:
>  Indicated writing power: 5
>  Is not unrestricted
>  Is not erasable
>  ATIP start of lead in:  -11649 (97:26/51)
>  ATIP start of lead out: 359849 (79:59/74)
> Disk type:    Long strategy type (Cyanine, AZO or similar)
> Manuf. index: 10
> Manufacturer: Lead Data Inc.
> Blocks total: 359849 Blocks current: 359849 Blocks remaining: 308791
> Starting to write CD/DVD at speed 4 in real TAO mode for single session.
> Last chance to quit, starting real write    0 seconds. Operation starts.
> Waiting for reader process to fill input buffer ... input buffer ready.
> BURN-Free is OFF.
> Performing OPC...
> Starting new track at sector: 0
> Track 01:   99 of   99 MB written (fifo 100%) [buf  89%]   4.9x.
> Track 01: Total bytes read/written: 104562688/104562688 (51056 sectors).
> Writing  time:  180.347s
> Average write speed   3.8x.
> Min drive buffer fill was 78%
> Fixating...
> Fixating time:   66.683s
> cdrecord: fifo had 1647 puts and 1647 gets.
> cdrecord: fifo was 0 times empty and 669 times full, min fill was 92%.
>
> Verifying Checksum of CDROM
>
> md5sum: /mnt/cdrom/root004: Input/output error
>
> bigbird /mnt: $dmesg
> , (=0x18db0), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=101296, (=0x18bb0), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=101184, (=0x18b40), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=83786, (=0x1474a), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=83274, (=0x1454a), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=83162, (=0x144da), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=83782, (=0x14746), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=83270, (=0x14546), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=83158, (=0x144d6), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=83486, (=0x1461e), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=82974, (=0x1441e), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=82862, (=0x143ae), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=83482, (=0x1461a), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=82970, (=0x1441a), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=82858, (=0x143aa), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=626, (=0x272), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=514, (=0x202), limit=2
> UDF-fs DEBUG misc.c:274:udf_read_tagged: block=256, location=256: read 
> failed
> UDF-fs DEBUG super.c:1216:udf_load_partition: No Anchor block found
> UDF-fs: No partition found (1)
> attempt to access beyond end of device
> 0b:00: rw=0, want=34, (=0x22), limit=2
> isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block=16
> MSDOS FS: IO charset iso8859-1
> MSDOS FS: Using codepage 850
> FAT: bogus logical sector size 0
> VFS: Can't find a valid FAT filesystem on dev 0b:00.
> FAT: freeing iocharset=iso8859-1
> MSDOS FS: IO charset iso8859-1
> MSDOS FS: Using codepage 850
> FAT: bogus logical sector size 0
> VFS: Can't find a valid FAT filesystem on dev 0b:00.
> FAT: freeing iocharset=iso8859-1
> EXT2-fs: Unrecognized mount option umask
> UDF-fs DEBUG lowlevel.c:57:udf_get_last_session: XA disk: no, 
> vol_desc_start=0
> UDF-fs DEBUG super.c:1426:udf_read_super: Multi-session=0
> UDF-fs DEBUG super.c:415:udf_vrs: Starting at sector 16 (2048 byte 
> sectors)
> attempt to access beyond end of device
> 0b:00: rw=0, want=34, (=0x22), limit=2
> UDF-fs DEBUG super.c:1162:udf_check_valid: Failed to read byte 32768. 
> Assuming open disc. Skipping validity check
> attempt to access beyond end of device
> 0b:00: rw=0, want=102112, (=0x18ee0), limit=2
> attempt to access beyond end of device
> 0b:00: rw=0, want=101600, (=0x18ce0), limit=2
> attempt to access beyond end of device
>
> .....
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
>
I just got it to work using:

  cdrecord -v -speed=2 -data -dev=1,0,0 ${IMAGE}.iso -driveropts=burnfree

My question now is:  Does burnfree make things easier or harder to 
work?  I don't want to do everything at speed=2.
But, I changed both options at once and don't know which one (or both) 
made the difference.
The drive is "rated" 12/10/32, but the 266MHz PII processor can't go 
that fast anyway.


Thanks.

Joe
_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug



More information about the nflug mailing list