Hi,
On Thu, 24 Jun 2021 14:18:08 +0200
"Thomas Schmitt" <scdbac...@gmx.net> wrote:
> Hi,
>
> i got an SCSI log of a failed burn run from Michael Lange.
>
> No artsy dance between drive and libburn is to see, which could explain
> a misunderstanding between both.
> The drive buffer becomes full, after 17 seconds some few sectors seem to
> have been actually written, and then the second next WRITE(10) fails
> with the "illegal request" error.
> Its data would not fit into the buffer, but the drive does not wait
> until there is room.
>
> So it has something to do with a full drive buffer.
>
> -------------------------------------------------------------------------
>
> cdrskin can avoid to fill the buffer by an old workaround from the bad
> old days of parallel ATA controllers when the CD burner blocked the
> hard disk on the same controller while a WRITE(10) was waiting for
> buffer space in the burner.
>
> I wonder whether this workaround can avoid the drive's error reply.
>
> If you are curious enough, add to your cdrskin runs this non-cdrecord
> option
>
> modesty_on_drive=1:min_percent=75:max_percent=80
burning failed with this option, too (two out of three runs).
Both of these failures seemed to occur at the same stage of the process
with the message
cdrskin: FATAL : SCSI error on write(299,13): See MMC \
specs: Sense Key 5 "Illegal request", ASC A8 ASCQ 04.
I think this means that it failed even a bit earlier than without this
option when it was "SCSI error on write(442,13)"?
Before it fails there is a real lot of log entries (about 3000 lines) like
READ BUFFER CAPACITY
5c 00 00 00 00 00 00 00 0c 00
>From drive: 12b
00 0a 00 00 00 12 00 00 00 04 10 00
342 us [ 26803073 ]
But maybe this is to be expected when cdrskin runs with the
modesty_on_drive=... option?
Best regards
Michael
