Hi all. I have been using cdrecord to make cd's for a while on my other system, but I just installed cdrtools-1.11a38 and I think I may have messed something up. I read the doc's and it doesn't seem like the developer likes linux too much.

Anywase, I got one cd burned just fine. Now, I can't burn any more, I get "cdrecord: CD/DVD-Recorder not ready" and after that I can't do anything to my drive.... not open it or anything. here's my cdrecord -scanbus:
Cdrecord 1.11a38 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'Compaq ' 'DVD-ROM DVD-114 ' '1.14' Removable CD-ROM
0,1,0 1) 'IDE-CD ' 'R/RW 4x4x24 ' 'C12a' Removable CD-ROM


and I am using this command to write:

cdrecord -v speed=4 dev=0,1,0 -data <image>

The reason I even started with all this is because I can't write the "color.gz" root file for slack onto a floppy... I've had problems with that before too... for some reason, I can't fill up the whole disk. here's the attributes of "color.gz":


-rw-r--r-- 1 root root 2333527 Sep 28 19:54 color.gz


Any help would be great.... I REALLY hope I didn't fry my cd-rw (I can still mount and read cd's from it though)

I hope you didn't fry it, does it give you OPC errors? If the system is "flushed" does cdrecord exhibit the same behavior? As the last resort I'd suggest downgrade and see if it fixes the problem. I just hope your burner didn't fall a victim of time and cdrecord as did mine a coupe of month ago, though I was getting OPC failed errors.

Thanks for the reply NEO. It turns out that 3 out of the 4 maxwell cd-rw's just aren't working for some reason. I am still kindof suspicious though... it doesn't seem like that should happen (plus, it works w/ windows cd creator).

Is there a way to eject the cd after one of those errors occurrs? Is that what you mean by "flushed"?

well, for now, I am using this script that I grabbed from here
http://www.tldp.org/HOWTO/CD-Writing-HOWTO.html
to check if the cd is o.k. :

#! /bin/bash

RD=/dev/scd0
for i in 32768,7 32776,32 32808,32 32958,128 33086,128 33214,128 \
33342,128 33470,32 33581,16 33598,16 33615,16 33632,16
do
old_IFS="$IFS"
IFS=","
set -- $i
IFS="$old_IFS"
OFFSET=$1
LENGTH=$2
echo "*`dd if=$RD bs=1 skip=$OFFSET count=$LENGTH 2> /dev/null`#"
done

#################################################

One more question though.... I tried to burn a data cd by piping the output of mkisofs straight to cdrecord and got this (last bit of the -v output):

Track 01: 400 MB written (fifo 4%) 4.0x. 84.72% done, estimate finish Sat Oct 26 12:00:32 2002
Track 01: 401 MB written (fifo 1%) 1.7x.cdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 03 22 01 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 13 00 00 00 00 0C 09 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x0C Qual 0x09 (write error - loss of streaming) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.028s timeout 40s

write track data: error after 420481024 bytes
Sense Bytes: 70 00 00 00 00 00 00 13 00 00 00 00 00 00 00 00 00 00
Writing time: 698.734s
Fixating...
Fixating time: 65.863s
cdrecord: fifo had 6687 puts and 6624 gets.
cdrecord: fifo was 15 times empty and 5675 times full, min fill was 0%.

I have a 500 Mhz, 128mb system... do you think that this is too slow to handle what I tried, or is there something going wrong?

ooh well... at least it's not TOTALLY fried.

thanks again for the reply

-Adam

Hmmm, it might choke on a slow machine, but it also depends on what concurrently runs on the system as well, I have a 450MHz machine with 128Mb of RAM, and I gave a try to mkisofs|cdrecord, well it choked on speed=6, it did find with speed=4 though, I have a Samsung internal CD-R/RW (32x10x40), and the above was performed on gentoo setup w/o X running, now I'll attempt to do the same on Athlon 850MHz with 512Mb of SDRAM running Slackware8.1 and see what happens, I am pretty sure the system will handle the speed=12 at least, I'll post back later cause I need to reconnect the burner.

I think that it was a system hangup rather than something else (I was in X). I had been following a how-to on creating a bootable cd, and the command they gave me to burn it was this:

mkisofs -R -l -L -D -b isolinux/isolinux.bin -c isolinux/boot.cat \
-no-emul-boot -boot-load-size 4 -boot-info-table -V "LFS_$(date +%Y%m%d)" \
$LFS | \
cdrecord -v -eject dev=0,0,0 speed=4 -

It scared the crap out of me. When I tried to do mkisofs --help to see what the hell was going on, there was too much for the screen. | less wouldn't work and > output.txt wouldn't either (really strange). I ended up just splitting it up and just sending the -o <image> option to mkisofs and it worked fine.

Anywase, thank you for helping me out w/ getting to the bottom of all this. I hope your cd-rw installation wasn't in vein.

-Adam

You should do

man mkisofs

instead.

If you like, you can grab my cdcopy script

http://jetblackz.freeservers.com/Installingcdcopy.html