cd ripping - was: cdrecord errors

2003-10-03 Thread Joachim Fahnenmueller
Hi Anthony,

I think the error is rather in CD ripping than in the burning process.

Try to rip with cdparanoia and describe what happens. 

BTW: Are these CDs copy protected?

On Fri, Oct 03, 2003 at 01:01:29AM +0100, Antony Gelberg wrote:
 Hi all,
 
 I'm going through some CD ripping with cdrecord, and grip.  I get quite
 a few tracks that cause problems - the face goes sad, and the speed goes
 down incredibly low.  I also get things like:
 
 scsi_read error: sector=103276 length=6 retry=1
  Sense key: 5 ASC: 64 ASCQ: 0
  Transport error: Illegal SCSI request (rejected by
 target)
  System error: Invalid argument
 scsi_read error: sector=103276 length=3 retry=2
  Sense key: 5 ASC: 64 ASCQ: 0
  Transport error: Illegal SCSI request (rejected by
 target)
  System error: Invalid argument
 
 Most of these discs do not appear to have any
 major marks or scratches.  Could a new CD-ROM sort it, or is cdrecord
 just very particular?
 
 Antony
 -- 

Regards,
-- 
Joachim Fahnenmüller
Lehrer für Mathematik und Physik

Herder-Gymnasium
Kattowitzer Straße 52
51065 Köln


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cd ripping - was: cdrecord errors

2003-10-03 Thread Antony Gelberg
On Fri, Oct 03, 2003 at 03:08:23PM +0200, Joachim Fahnenmueller wrote:
 Hi Anthony,
 
 I think the error is rather in CD ripping than in the burning process.
 
 Try to rip with cdparanoia and describe what happens. 
 
 BTW: Are these CDs copy protected?

Sorry, I was a bit tired when I wrote my original email.  grip does
indeed rip with cdparanoia and the errors I described do come from that
process.  Does that help at all?

A


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



cdrecord errors

2003-10-02 Thread Antony Gelberg
Hi all,

I'm going through some CD ripping with cdrecord, and grip.  I get quite
a few tracks that cause problems - the face goes sad, and the speed goes
down incredibly low.  I also get things like:

scsi_read error: sector=103276 length=6 retry=1
 Sense key: 5 ASC: 64 ASCQ: 0
 Transport error: Illegal SCSI request (rejected by
target)
 System error: Invalid argument
scsi_read error: sector=103276 length=3 retry=2
 Sense key: 5 ASC: 64 ASCQ: 0
 Transport error: Illegal SCSI request (rejected by
target)
 System error: Invalid argument

Most of these discs do not appear to have any
major marks or scratches.  Could a new CD-ROM sort it, or is cdrecord
just very particular?

Antony
-- 
Now playing: Spock's Beard - Onomatopoeia


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



cdrecord errors...

1999-02-28 Thread Steve Beitzel
Hello all,

I have been trying to burn a particular image to CD for the last 4
hours now.  In the process, I have killed 5 CD's from the same bundle.
cdrecord gets about 25-30% done with the burn, and then it gives output
like this:

Waiting for reader process to fill input-buffer ... input-buffer ready.
Starting new track at sector: 0
cdrecord: Success. write_g1: scsi sendcmd: retryable error
CDB:  2A 00 00 02 2B D0 00 00 10 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 03 00 00 00 00 0A 00 03 A4 DE 02 FF 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x02 Qual 0xFF (no seek complete) [No matching qualifier] Fru
0x0
Sense flags: Blk 0 (valid)
cmd finished after 6.077s timeout 40s

write track data: error after 291405824 bytes
Sense Bytes: F0 00 00 00 00 00 00 0A 00 03 A9 8D 00 00 00 00 00 00
Writing  time:  969.163s
Fixating...
cdrecord: Success. close track/session: scsi sendcmd: retryable error
CDB:  5B 00 02 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 05 00 00 00 00 0A 00 03 A9 95 2C 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x2C Qual 0x00 (command sequence error) Fru 0x0
Sense flags: Blk 0 (valid)
cmd finished after 0.008s timeout 480s
Fixating time:0.009s
cdrecord: fifo had 9021 puts and 8894 gets.
cdrecord: fifo was 0 times empty and 8789 times full, min fill was 70%.

...

I doubt that the drive is damaged, because I wrote a CD earlier today and
it worked perfectly.  I also doubt that it is the fault of Linux, because
when I tried to burn the same CD from Windows, it hung after getting
through about 30% of the burn.  The CD-RW is a Memorex CRW-1622 using
IDE-SCSI on Kernel 2.2.2.  Any ideas, or do I have a bad batch of CD's
here?

Thanks,

Steve


Re: cdrecord errors...

1999-02-28 Thread Daniel J. Brosemer
On Sun, 28 Feb 1999, Steve Beitzel wrote:

 Hello all,
 
   I have been trying to burn a particular image to CD for the last 4
 hours now.  In the process, I have killed 5 CD's from the same bundle.
 cdrecord gets about 25-30% done with the burn, and then it gives output
 like this:

[errors snipped]

 ...
 
 I doubt that the drive is damaged, because I wrote a CD earlier today and
 it worked perfectly.  I also doubt that it is the fault of Linux, because
 when I tried to burn the same CD from Windows, it hung after getting
 through about 30% of the burn.  The CD-RW is a Memorex CRW-1622 using
 IDE-SCSI on Kernel 2.2.2.  Any ideas, or do I have a bad batch of CD's
 here?

Have you tried recreating the image?  What program are you using under
windoze?  I had one image once that would refuse to burn with cdrecord,
but burned fine with cdrwin--go figure.  I've also had probably about five
images that went the other way (cdrecord was fine, but cdrwin had
problems).  Chances are you don't have a bad batch of CD's.  If they're
AZO (blue back) take a look for imperfections on the bottom, but this
doesn't sound like a CD problem.  Another suggestions is -dummy is your
friend.  When testing this (Especially after you have toasted one disc, do
test-burns to make sure you don't toast any more!)

Good Luck!

-Dano


Re: cdrecord errors...

1999-02-28 Thread Steve Beitzel
Hello again,

I have remade the image, about five times or so.  No luck :(  I
was using Adaptec Easy CD Creator 3.01 to try and burn it from windows.
One interesting thing I noticed however, was the while in windows, it
didn't just kill the CD like normal, it hung at a certain point in the
burn process -- not hung as in crashed, but rather, it didn't make any
progress after a certain point.  I let it sit there for about 15 minutes
before I killed the process.  That is what led me to believe that I had a
bad batch of CD's.  Any other suggestions?

Thanks,

Steve

On Sun, 28 Feb 1999, Daniel J. Brosemer wrote:

 On Sun, 28 Feb 1999, Steve Beitzel wrote:
 
  Hello all,
  
  I have been trying to burn a particular image to CD for the last 4
  hours now.  In the process, I have killed 5 CD's from the same bundle.
  cdrecord gets about 25-30% done with the burn, and then it gives output
  like this:
 
 [errors snipped]
 
  ...
  
  I doubt that the drive is damaged, because I wrote a CD earlier today and
  it worked perfectly.  I also doubt that it is the fault of Linux, because
  when I tried to burn the same CD from Windows, it hung after getting
  through about 30% of the burn.  The CD-RW is a Memorex CRW-1622 using
  IDE-SCSI on Kernel 2.2.2.  Any ideas, or do I have a bad batch of CD's
  here?
 
 Have you tried recreating the image?  What program are you using under
 windoze?  I had one image once that would refuse to burn with cdrecord,
 but burned fine with cdrwin--go figure.  I've also had probably about five
 images that went the other way (cdrecord was fine, but cdrwin had
 problems).  Chances are you don't have a bad batch of CD's.  If they're
 AZO (blue back) take a look for imperfections on the bottom, but this
 doesn't sound like a CD problem.  Another suggestions is -dummy is your
 friend.  When testing this (Especially after you have toasted one disc, do
 test-burns to make sure you don't toast any more!)
 
 Good Luck!
 
 -Dano
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null