[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dead CD-R burn...
I use HP Surestore 6020.
I saw a lot of messages concerning HP7100 in the linux.apps.cdwrite
discussion group. I suggest you forward a question to this user group.
Yaniv Kimchi
yaniv@zvia.org.il
On Thu, 3 Sep 1998, Ze'ev Maor wrote:
> As I said in my message, I also tried preparing the image on the disk
> and then burning it, that didn't work as well, also I didn't get any error
> messages about buffer underrun, so this can't be the problem...
>
> What CD-R did you use???
>
> -----Original Message-----
> From: Yaniv Kimchi <yaniv@zvia.org.il>
> To: Ze'ev Maor <gmaor@techunix.technion.ac.il>
> Cc: linux ILUG <linux-il@cs.huji.ac.il>; ILUG Mailing List
> <linux-il@linux.org.il>
> Date: יום חמישי 03 ספטמבר 1998 07:41
> Subject: Re: Dead CD-R burn...
>
>
> >It is highly recommended to first preopare the image with mkisofs.
> >check it with loopback device and only then burn it.
> >Most CD-R's depend on the speed their internal buffer is being fed.
> >If there is a delay the CD will be unusable.
> >Try to run mkisofs to a disk image,
> >Then test it with
> >mount -t iso9660 -o ro,loop=/dev/loop0 imganame /mntpoint
> >Only then run cdrecord from the Image.
> >
> >I have burned this way Hundreds of CD's under Linux without a single
> >problem.
> >
> >Yaniv Kimchi
> >yaniv@zvia.org.il
> >
> >On Thu, 3 Sep 1998, Ze'ev Maor wrote:
> >
> >> I've tried to burn a couple of CD-Rs with little to no success.
> >>
> >> Here's what I did, maybe someone can help:
> >>
> >> I'm using the HP-SureSture7100e, I've compiled paride+epat+pg as
> >> modules, loaded them, and the pg driver successfuly identified my
> >> CD-R. I've patched 'cdrecorder' with the scsi-linux-pg.c support and
> >> re-compiled it. I've done a few 'dummy' tests to make sure
> >> everything is ok, and got no error messages, up to now, as smooth
> >> as it gets (well, it did take 5 hours....;-).
> >>
> >> Then I wanted to burn a couple of dirs from my CD-ROM and used
> >> the following command:
> >>
> >> mkisofs -r /cdrom | cdrecord -v -multi fs=15m speed=2 dev=0 -
> >>
> >> the process started and seemed to work fine...following are the last log
> >> lines of the burning:
> >>
> >> 87.68% done, estimate finish Thu Sep 3 04:16:01 1998
> >> 92.05% done, estimate finish Thu Sep 3 04:16:03 1998
> >> 96.44% done, estimate finish Thu Sep 3 04:16:04 1998
> >> Total extents actually written = 114066
> >> Total translation table size: 0
> >> Total rockridge attributes bytes: 1325
> >> Total directory bytes: 4096
> >> Path table size(bytes): 44
> >> Max brk space used 4000
> >> 114066 extents written (222 Mb)
> >> Track 01: 222 MB written (fifo 100%).
> >> Track 01: Total bytes read/written: 233607168/233607168
> >> (114066 sectors).
> >> Writing time: 771.631s
> >> Fixating...
> >> Fixating time: 137.099s
> >> cdrecord: fifo had 7131 puts and 7131 gets.
> >> cdrecord: fifo was 0 times empty and 6618 times full, min fill was
> >> 95%.
> >>
> >>
> >> All seems great isn't it?? So why is it that after all this the media
> >> died, I couldn't mount it (no media / unknown media / CD-ROM
> >> won't stop spinning etc.) + I couldn't get the TOC with 'cdrecord -toc
> >> dev=0'.
> >>
> >> I've also tried creating small images with 'mkisofs' and burning them,
> >> but the result was the same.
> >>
> >> Can anyone help???
> >>
> >>
> >
>