cdr write fail with cdrecord and x-cdroast

From: lionelhasselhoff (lionelhasselhoff_at_hotmail.com)
Date: 07/22/03


Date: 21 Jul 2003 21:40:59 -0700

My computer setup is a PIII with a Khypermedia IDE CDR, running a dual
boot system with W98 and Red Hat 8.0. I have been trying to burn some
Linux operating system ISOs and have run into several problems. I am
using W98 as the OS for my internet connection, so the ISOs are
downloaded onto a DOS partition. I thought this wouldn't matter at
all, and apparently it didn't to X-CDRoast, but it may have to
cdrecord. I'll ask the main question at the beginning of this
message, and give the background info below. The question is: when
using cdrecord to burn a linux ISO to CDR from a DOS partition, do I
need to throw a command line switch, or do something else in order to
make the filesystem Linux compatible?

I have had no filesystem incompatibility or bad superblock errors when
using X-CDRoast, it just doesn't seem to be especially compatible with
my drive -- fixating and coasterizing disks on 50% of power
calibration failures, which happens about 50% of the time when I try
to burn a disk. Nero, the Windows software that was bundled with the
drive has frequent OPC failures but does not fixate the disk
afterwards.

I started by using X-CDRoast, and while it gave me the occasional OPC
/ power calibration failure, I managed to burn five ISO to disk
without losing any media. Today I am trying to burn the sixth and
final disk of the set and it isn't happening for me.

X-CDRoast failed twice, getting through the power calibration, then
writing for a second or two, and then encountering some kind of error,
giving the typical "device not available error" and then fixating the
disk, coasterizing it. Trying to cancel the write when it happened
the second time just made the system hang, it didn't save the blank.
It did this twice in a row, so I decided to try cdrecord without the
GUI.

cdrecord -v dev=0,0,0 speed=4 (or 8) <filename.iso>

made for one OPC failure, and then a successful burn which fixated the
disk and exited. But when I tried to mount the disk it told me that
it was the wrong file system type, had a bad superblock, or had some
other kind of error that I can't remember at the moment.

I had encountered this before (as well as some of the other problems
described above) with a bad drive of the same model. That drive
eventually failed completely and I had to return it for this new one.
So far, I'm not very impressed with the operation of this drive under
Linux or Windows.

Thinking that this was a repeat of the coasterizing error, I tried to
write the ISO again at 8x speed, and had another apparently successful
burn that returned the same wrong file system type error message.

I decided to check whether the ISO could be written under Windows, and
while I was at it, I checked to see if I could read the "wrong file
system type" disks under Windows. I could, the ISO appeared to be
there without any missing files or errors or anything. Unfortunately
when trying to use Nero to write the ISO, it came back with a
"unexpected filesystem" error, and wouldn't queue up the ISO for
burning.

Does anyone know what is going on here? Is there a commandline option
that I am missing with cdrecord that will create a ext3fs, or other
Linux filesystem from the ISO? Does the ISO being on a DOS partition
have anything to do with it? Would it help to copy the ISO to a Linux
native filesystem? Or is it just problems between cdrecord/the
driver/my drive? Anyone have any experience using a Khypermedia
48x24x48 Seamless Link CDR? Particularly under Linux? Are they
really this unreliable? It is hard to believe that I just happened to
get two lemons in a row.

Thanks,

Barton



Relevant Pages

  • Re: cdr write fail with cdrecord and x-cdroast
    ... I have been trying to burn some Linux operating system ... > frequent OPC failures but does not fixate the disk afterwards. ... Particularly under Linux? ...
    (comp.os.linux.hardware)
  • Re: CD disk image not recognized by Disk Utility
    ... file) from http://www.mikedickson.org.uk/codetalkers/ but Tiger's Disk Utility does not recognize it and consequently is ... Put the "iso", cue, and cdt files in the same directory In your terminal of choice, type drutil burn ... Must specify a valid image path (dmg, iso, cue/bin, and toc). ... I tried munging the .cue file in various ways, and after I deleted the block os REM lines the drutil command worked and produced a working CD. ...
    (uk.comp.sys.mac)
  • Re: CD disk image not recognized by Disk Utility
    ... burn it to an audio CD. ... Must specify a valid image path (dmg, iso, cue/bin, and toc). ... I tried munging the .cue file in various ways, ... disk image of "Codetalkers" to burn on Mac. ...
    (uk.comp.sys.mac)
  • Re: CD disk image not recognized by Disk Utility
    ... CDT file) from http://www.mikedickson.org.uk/codetalkers/ but Tiger's Disk Utility does not recognize it and consequently is ... Put the "iso", cue, and cdt files in the same directory In your terminal of choice, type drutil burn ... Must specify a valid image path (dmg, iso, cue/bin, and toc). ... I tried munging the .cue file in various ways, and after I deleted the block os REM lines the drutil command worked and produced a working CD. ...
    (uk.comp.sys.mac)
  • [Fwd: 6.06 ppc desktop iso size.....]
    ... so that i could burn it to cd and use it on my powerbook. ... the image downloads and its final size in 701MB, ... cd in to my drive, right click the image, and select write to disk. ... transfer the iso to my powerbook, and burn it in OSX, on the exact same ...
    (Ubuntu)