cdrecord-prodvd ALWAYS fails to burn

whysyn · 09-07-2005, 09:43 AM

I have tried all kinds of different command lines, drive configurations, etc. and don't really have a good history of what I've tried.

It always makes from about 75 to 150 meg into the burn, and then fails.

Here's the latest command line I'm running:
[root@local root]# cdrecord-prodvd dev=0,0,0 driveropts=burnfree speed=4 -v -dao /var/backup/200506.iso

and here is the resulting output:

Code:

Cdrecord-ProDVD-Clone 2.01b31 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jï¿½rg Schilling
Unlocked features: ProDVD Clone
Limited  features:
This copy of cdrecord is licensed for: private/research/educational_non-commercial_use
TOC Type: 1 = CD-ROM
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.8'.
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'SONY    '
Identifikation : 'DVD RW DW-D22A  '
Revision       : 'BYS2'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: DVD-R sequential recording
Profile: Unknown
Profile: DVD+R
Profile: DVD+RW
Profile: DVD-RW sequential overwrite
Profile: DVD-RW restricted overwrite
Profile: DVD-R sequential recording (current)
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R
Profile: CD-ROM
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW driver (mmc_dvd).
Driver flags   : DVD MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: PACKET SAO
Drive buf size : 1563904 = 1527 KB
FIFO size      : 4194304 = 4096 KB
Track 01: data  1938 MB
Total size:     1938 MB = 992270 sectors
Current Secsize: 2048
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 1306226
Forcespeed is OFF.
Starting to write CD/DVD at speed 4 in real SAO 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 ON.
Starting new track at sector: 0
Track 01:   91 of 1938 MB written (fifo  95%) [buf  44%]   2.2x.cdrecord-prodvd: Input/output error. write_g1: scsi sendcmd: no error
CDB:  2A 00 00 00 B7 56 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 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 0 (not valid)
cmd finished after 18.998s timeout 100s

write track data: error after 96120832 bytes
cdrecord-prodvd: A write error occured.
cdrecord-prodvd: Please properly read the error message above.
Writing  time:  130.009s
Average write speed  11.3x.
Min drive buffer fill was 5%
Total of 1 possible drive buffer underruns predicted.
Fixating...
Fixating time:    0.000s
BURN-Free was not used.
cdrecord-prodvd: fifo had 1578 puts and 1515 gets.
cdrecord-prodvd: fifo was 0 times empty and 31 times full, min fill was 84%.

Bruce Hill · 09-07-2005, 09:54 AM

This always works for me burning DVDs from iso images:

Code:

/usr/bin/growisofs -dvd-compat -Z /dev/hdb=slackware-10.1-DVD.iso

I must admit I've never used "driveropts=burnfree" with growisofs,
though I use it every time burning CDs with cdrecord. Another good
benefit of growisofs is that it is not one of Jörg Schilling's apps. Which
means that it works well with Linux, and gives no phony error messages.

whysyn · 09-07-2005, 10:01 AM

Thanks for the quick reply!

I never really liked cdrecord-prodvd... but it worked well most of the time on the last system I had running.

I don't have growisofs... is it part of a larger package? RPMfind isn't coming up with anything when I search for it...

Bruce Hill · 09-07-2005, 10:12 AM

Gosh, mate, I don't know what growisofs is a part of, but it's in Slackware
when you do a full install, and your UserCP says Slackware is your distro.

Bruce Hill · 09-07-2005, 10:22 AM

I think it's a part of dvd+rw-tools. More stuff than you'll ever want to read
is available here > http://fy.chalmers.se/~appro/linux/DVD+RW/

whysyn · 09-07-2005, 10:27 AM

Got it, thank you.

Primary systems for my wife and myself are Slack, but this new system I'm using for backup and such is RedHat *hangs head in shame*

Bruce Hill · 09-07-2005, 10:33 AM

I have a server that uses Slackware-10.1. I backup all our comps with cron
jobs running rsync scripts, plus rsync Slackware -current and another guy's
server to that box. Slack works great for me.

whysyn · 09-07-2005, 11:12 AM

sorry to keep bothering you, but i got dvd+rw-tools installed, and kjust tried to burn a disk.

command:

Code:

[root@local root]# growisofs -dvd-compat -speed=1 -Z /dev/cdrom=/var/backup/200506.iso

output on my terminal (stopped and sat there for a while):

Code:

Executing 'builtin_dd if=/var/backup/ready_to_burn/200412idssys-adssys-wgports.iso of=/dev/cdrom obs=32k seek=0'
/dev/cdrom: "Current Write Speed" is 8.0x1385KBps.
         0/2032168960 ( 0.0%) @0x, remaining ??:??
         0/2032168960 ( 0.0%) @0x, remaining ??:??
         0/2032168960 ( 0.0%) @0x, remaining ??:??
         0/2032168960 ( 0.0%) @0x, remaining ??:??
         0/2032168960 ( 0.0%) @0x, remaining ??:??
         0/2032168960 ( 0.0%) @0x, remaining ??:??
         0/2032168960 ( 0.0%) @0x, remaining ??:??

Hmm, it seems to ignore the "speed=" argument, and I got a core dump on the console of the machine...

Bruce Hill · 09-07-2005, 11:16 AM

I always used it that one way, full path to the command, as root, and never
gave it speed or burnfree arguments. I also give it the device name, and
not the symlink (/dev/cdrom). You might want to issue "dmesg | grep -i dvd"
to determine where your device is located.

whysyn · 09-07-2005, 11:50 AM

To your knowledge, do I still need the "hdg=ide-scsi" kernel parameter on boot?

Thanks again for all the help!

Bruce Hill · 09-07-2005, 11:57 AM

What kernel are you using? I don't remember which one saw my drive as
hdg but it does sound familiar. With the 2.6 series kernels, you definitely
do not need ide-scsi. I think you don't need it from kernel 2.4.27 and after.

Do you have a SATA drive? If so, it should now be seen as /dev/sda with
a 2.6 series kernel.

There were also some problems, especially with cdrecord, up until kernel
2.6.8.1 I believe.

whysyn · 09-07-2005, 12:13 PM

It's RedHat's 2.4.20-8 kernel, old I know... but I don't like to change things until there is a compelling reason... this just might motivate me to upgrade.

There are no SATA drives in the system... but 4 IDE channels. I have the system drive on channel 3 master (hde) and the DVD burner on channel 4 master (hdg). I don't remember why I didn't use channels 1 and 2. The system has been running stable for months, but I'm running out of drive space, which is why I'm trying to burn DVD's now...

Why I set the system up, I knew I would need to burn down the road, which is why I set up ide-scsi emulation. The system that was replaced by this one was running almost exactly the same config, but was on RH7.3, this one is RH9.0.

I'm rebooting now without ide-scsi and will try growisofs again. If I ruin another disk, oh well, I have plenty of blanks I picked up cheap...

EDIT: Man, I hate RedHat... if this were a Slack system, I'd have a new, custom compiled kernel up and running in about 15 minutes...

Bruce Hill · 09-07-2005, 12:25 PM

I never used a kernel that old with DVDs, but you will need SCSI emualtion
for burning CDs. And you can always compile a new kernel, and keep your
old one, also. No need to do away with it. I would recommend using this
Kernel Build Guide and by all means build the kernel under your /home
directory. Linus wrote specific instructions about that to be found in
./linux-2.x.x.x/README. In fact, his instructions serve me well, and I've
been building my kernels in /home/mingdao/build/ for quite some time.

Get the latest stable kernel and bring that box up-to-date.

whysyn · 09-07-2005, 01:49 PM

I had started a burn before I ready your reply... no scsi emulation, burned fine!

Maybe RedHat has some patches in their updated 2.4.20 kernel to account for this. They like to hack the heck out of everything...

Bruce Hill · 09-07-2005, 06:21 PM

Well, growisofs didn't need SCSI emulation, but I think
cdrecord does. Some of these distributions have people
they pay working on the kernel, and they get patches that
the rest of us don't get. For instance, in SuSE, "uname -a"
displays everything properly, but the version of coreutils
the rest of us gets isn't patched, and that one displays

Code:

Linux titus 2.6.13 #1 Fri Sep 2 08:40:45 CST 2005 i686 unknown unknown GNU/Linux

The processor type and hardware platform are missing.
The maintainer for coreutils works for SuSE, and it all
displays in that distro.