Here is some extra information:
-> the audio CD I tried to copy was pretty bad. trying to extract the last
track with cdparanoia correction of 3 failed miserably (stalling for ages).
copying with CDRDAO without error correction failed because of CRC errors
while extracting the TOC (only extracting the sound with cdparanoia works
however) => i'll give up copying this CD on the fly. even though it works
very well in a hi-fi.
-> using plextor or plextor-scan fails with my drive (it's a plextor DVD-106
and the doc says that for DVD-104 and DVD-105 you should use generic-mmc so i
guess it's ok) .
-> trying another CD without error correction, i got a 5.6x copy speed. that's
still not good enough since my burner can do 8x at minimum, so copying a 5.6x
requires using burnproof which is not good. i'll try to rearrange the cables
(i already have DMA on all drives).
so it seems it was only a very bad medium and cdparanoia stalling for very
trying another CD i also got one cdrdao ASSERT, i'll send it in another mail.
PS: on the CD i tested first, i could extract a 600k/s with error correction
(and stalling on the last track), and 1.4M/s without error correction.
 plextor extracts the toc quite fast and then gets errors for each block
copied. plextor-scan says "error setting block size", extracts the toc
instantaneously and then copies at 11x.. but it doesn't read the source CD at
On Monday 31 of March 2003 21:48, Giuseppe Corbelli wrote:
> You should first try plextor or plextor-scan as drivers for your reader.
> > Anyway, I have two questions:
> > -> first and foremost, the copy failed and I had messages from cdrdao
> > about a hardware error:
> > --------------------------------------------
> > ?: Input/output error. : scsi sendcmd: no error
> > CDB: BE 00 00 02 8A 50 00 00 1A F8 02 00
> > status: 0x2 (CHECK CONDITION)
> > Sense Bytes: F0 00 04 00 02 8A 50 0A 00 00 00 00 09 01 00 00
> > Sense Key: 0x4 Hardware Error, Segment 0
> > Sense Code: 0x09 Qual 0x01 (tracking servo failure) Fru 0x0
> > Sense flags: Blk 166480 (valid)
> > cmd finished after 0.470s timeout 20s
> > -----------------------------------------------
> > (i have about 10 of them in my log before I killed the burning, the log
> > is attached to this message)
> > what does it mean? would my CD reader/burner be deficient? (and which
> > one? reader or burner??) is it really a hardware error or a linux kernel
> > bug or a cdrdao bug?
> > my linux kernel version is quite ancient (2.4.3-20mdk).
> Seems not a kernel-related issue, but you should definitely upgrade to
> 2.4.19 or 20 to narrow the possibilities.
> > ->before it failed, it was burning at 3x which is quite slow (I wanted 8x
> > which is the minimum speed at which my burner can burn anyway). The
> > buffer was constantly at 3-6%. did i misconfigure something? Any idea
> > what I could do to improve this deceiving performance, or is it normal?
> > Maybe make the buffer bigger (where in the GUI?)
> I don't know about the GUI. The speed was slow because the reader couldn't
> keep up with the burner. Having BURNPROOF on the burner stops when its
> buffer gets empty.
> Anyway, the errors reported come from the reader, and usually mean
> "defective hardware".
> Try a cdrdao read-cd with plextor or plextor-scan and see the results.
> Update the kernel. Try cdda2wav to extract some tracks from this very same
> CD and see what happens.
"If there is any kind of God, it's not in you or in me,
but in the space between us"
-- Celine, "Before Sunrise"
(It's not about what you do, it's about what you give.)