On Wed, 2002-10-09 at 00:56, Michael Fratoni wrote: > On Wednesday 09 October 2002 12:06 am, Chris Kloiber wrote: > > > # cdrecord -v -dao -eject dev=0,0,0 speed=12 your_image_here.iso > > > > (get the dev= from 'cdrecord -scanbus') > > > > Does the output indicate you can't do dao? If not, it's time to get a > > new burner. > > No, that's what's driving me nuts. No indication that DAO isn't supported, > but there is a warning that appears. I suspect that has something to do > with the problem. The warning is: > Sending CUE sheet... > cdrecord: WARNING: Drive returns wrong startsec (0) using -150 > Writing pregap for track 1 at -150 > Starting new track at sector: 0 Harmless. Don't let that worry you. cdrecord is doing the right thing. > Trying to get the md5sum on the cd results in: > md5sum /dev/cdrom > md5sum: /dev/cdrom: Input/output error I'm assuming the generated md5 does not match the published MD5SUM? Have you tried reading the cd back in and testing it with md5sum? # readcd dev=0,0,0 f=test.iso && md5sum test.iso What does 'linux mediacheck' tell you about the cd? > A quick search on the web, and I found a message suggesting that this is > most likely a firmware bug. The post is regarding the same error on a > different manufactures drive, but seems a likely answer. > http://www.mail-archive.com/cdwrite@other.debian.org/msg02500.html -- Chris Kloiber
