rbw wrote:
I'm having a problem writing DVD iso images to DVD-R media. I'm looking for some input on what I am doing wrong and some tips on what to do next. Here is what I have going on so far...

dmesg says
hdc: ATAPI 24X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20

KInfoCenter says:
Can Write DVD-R      YES
Can Write DVD-RAM   YES

I read this:
http://osdir.com/ml/debian.knoppix/2004-06/msg00067.html
to get this:
growisofs -dvd-compat -Z /dev/hdc=KNOPPIX_V5.1.1DVD-2007-01-04-EN.iso

This is the same command line that I use for my burns. I have a Sony DVD drive.

After making a couple coasters I searched and found tkDVD (http://regis.damongeot.free.fr/tkdvd/) and it shows you the CLI it builds. In this case specifically for burning a DVD images it creates this: growisofs -dvd-compat -use-the-force-luke=tty -Z /dev/dvd=KNOPPIX_V5.1.1DVD-2007-01-04-EN.iso

What kind of media are you using? I had been using the Fry's GQ stuff and the DVD-R discs had about a 10% failure rate for me. I switched to DVD+R and haven't had a bad burn yet out of about 100.

BTW I got "KNOPPIX_V5.1.1DVD-2007-01-04-EN.iso" via bittorrent using Azureus (twice)

Both the CLI and tkDVD produce output similar to the following during the burn process...

growisofs -dvd-compat -Z /dev/hdc=KNOPPIX_V5.1.1DVD-2007-01-04-EN.iso
Executing 'builtin_dd if=KNOPPIX_V5.1.1DVD-2007-01-04-EN.iso of=/dev/hdc obs=32k seek=0'
/dev/hdc: "Current Write Speed" is 8.2x1352KBps.
          0/4232019968 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU   0.0%
          0/4232019968 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU   0.0%
          0/4232019968 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU   0.0%
          0/4232019968 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU   0.0%
          0/4232019968 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU   0.0%
11272192/4232019968 ( 0.3%) @2.4x, remaining 131:03 RBU 100.0% UBU 2.9%
   27295744/4232019968 ( 0.6%) @3.5x, remaining 64:11 RBU  99.2% UBU 100.0%
   43417600/4232019968 ( 1.0%) @3.5x, remaining 45:01 RBU 100.0% UBU 100.0%
   59670528/4232019968 ( 1.4%) @3.5x, remaining 36:07 RBU 100.0% UBU 100.0%
   76054528/4232019968 ( 1.8%) @3.6x, remaining 31:52 RBU 100.0% UBU  97.1%
   92569600/4232019968 ( 2.2%) @3.6x, remaining 28:19 RBU 100.0% UBU 100.0%
  109215744/4232019968 ( 2.6%) @3.6x, remaining 25:47 RBU 100.0% UBU 100.0%
...
4180213760/4232019968 (98.8%) @3.0x, remaining 0:07 RBU 100.0% UBU 100.0%
 4194172928/4232019968 (99.1%) @3.0x, remaining 0:05 RBU  99.8% UBU 100.0%
 4208132096/4232019968 (99.4%) @3.0x, remaining 0:03 RBU  99.8% UBU 100.0%
 4222058496/4232019968 (99.8%) @3.0x, remaining 0:01 RBU  59.4% UBU 100.0%
builtin_dd: 2066416*2KB out @ average 5.1x1352KBps
/dev/hdc: flushing cache
/dev/hdc: updating RMA
/dev/hdc: closing disc

The system that does the burn "sees" the blank DVD-R media before the burn and then doesn't recognize the media after the burn. The system dedicated to booting from Knoppix using Knoppix v5.11 on CD-ROM doesn't boot from the DVD-R at all (tested on 2 different systems).

Are you using GNOME for a desktop? It's possible that the piece that auto-recognizes the DVD-R as being blank is interfering with the burn.

I'm stumped...

Which part of the burn is bad, i.e. the beginning or the end? To find out, use this handy script that Carl Lowenstein made a while back for this purpose:

<---- begin ----->
#!/bin/sh
# Author: Carl Lowenstein
# $Id: isocmp,v 1.1 2006/04/03 21:19:09 cdl Exp $
# isocmp
# compare image on burned {cd,dvd} with its source file
# size=$(isosize -d 2048 $2)
# don't use isosize, in case the image is not really iso9660

case $# in
       2) ;;
       *) echo "usage:  $0 /dev/cdrom /source/file.iso"; exit 2;;
esac

# a few sanity tests
if test ! -r $1
       then echo "can't read $1"; exit 2
fi
if test ! -r $2
       then echo "can't read $2"; exit 2
fi
if test ! -f $2
       then echo "$2 is not a file"; exit 2
fi

# compute size of file in 2kB blocks
size=$( dc -e "$(ls -l $2 | gawk '{print $5}') 2048/p")



# do the real work here, compare device file and source file byte by byte
dd if=$1 bs=2k count=$size | cmp -s $2 -

# report result
case $? in
       0) echo "good"; exit 0;;
       *) echo "bad"; exit 1;;
esac

<---- end ----->


You might have to slow down the DVD burner. Some media/burner combinations can't do their advertised speed. Try using the -speed=1 option. This will be really slow but may get you a good burn.

The other thing to watch out for is system activity that causes I/O operations. I have found that my burner is very sensitive to having the source hard drive in use while burning an image from it. Keep an eye on the buffer numbers and if they drop below about 50% while burning be suspicious. See if you can get a fairly quiescent system before doing a burn.

Gus


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to