Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #236431

Re: Fatal error while burning CD

From Michael Lange <klappnase@freenet.de>
Newsgroups linux.debian.user
Subject Re: Fatal error while burning CD
Date 2021-06-25 00:50 +0200
Message-ID <CtGkx-vv-1@gated-at.bofh.it> (permalink)
References <CtuCK-1L6-11@gated-at.bofh.it> <CtwuR-2U1-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi,

On Thu, 24 Jun 2021 14:18:08 +0200
"Thomas Schmitt" <scdbackup@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

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-23 19:40 +0200
  Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-23 21:00 +0200
    Re: Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-23 23:40 +0200
      Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-24 09:20 +0200
        Re: Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-24 11:30 +0200
          Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-24 12:20 +0200
            Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-24 14:20 +0200
              Re: Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-25 00:50 +0200
                Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-25 08:50 +0200
                Re: Fatal error while burning CD Michael Lange <klappnase@freenet.de> - 2021-06-25 10:30 +0200
                Re: Fatal error while burning CD "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-25 11:50 +0200
                Re: Fatal error while burning CD mcgarrett <dmcgarrett@optonline.net> - 2021-06-26 04:00 +0200
        How to verify newly burned disc [Was: Fatal error while burning CD] Michael Lange <klappnase@freenet.de> - 2021-06-29 10:30 +0200
          Re: How to verify newly burned disc [Was: Fatal error while burning          CD] Linux-Fan <Ma_Sys.ma@web.de> - 2021-06-29 10:40 +0200
            Re: How to verify newly burned disc [Was: Fatal error while burning  CD] Michael Lange <klappnase@freenet.de> - 2021-06-29 11:10 +0200
          Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-29 12:10 +0200
            Re: How to verify newly burned disc Michael Lange <klappnase@freenet.de> - 2021-07-02 09:10 +0200
          Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-07-02 12:30 +0200
            Re: How to verify newly burned disc Michael Lange <klappnase@freenet.de> - 2021-07-02 20:00 +0200
              Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-07-02 21:30 +0200
                Re: How to verify newly burned disc Michael Lange <klappnase@freenet.de> - 2021-07-03 01:00 +0200
                Re: How to verify newly burned disc Stefan Monnier <monnier@iro.umontreal.ca> - 2021-07-03 04:50 +0200
                Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-07-03 10:50 +0200
          Re: How to verify newly burned disc [Was: Fatal error while burning CD] Richmond <richmond@criptext.com> - 2021-07-02 22:20 +0200
            Re: How to verify newly burned disc [Was: Fatal error while burning  CD] Greg Wooledge <greg@wooledge.org> - 2021-07-02 22:40 +0200
              Re: How to verify newly burned disc [Was: Fatal error while burning  CD] Richmond <richmond@criptext.com> - 2021-07-02 23:30 +0200
                Re: How to verify newly burned disc [Was: Fatal error while burning  CD] Greg Wooledge <greg@wooledge.org> - 2021-07-02 23:40 +0200
                Re: How to verify newly burned disc "Thomas Schmitt" <scdbackup@gmx.net> - 2021-07-03 00:00 +0200

csiph-web