Comment 11 for bug 1896804

Hi Thomas.

did the alteration to spc.c and ran make. ububnu is still seeing the
drive as read only. see the output below.

chris@chris-A320M-S2H-V2:~/xorriso/xorriso-1.5.3$ ./xorriso/xorriso
-outdev /dev/sr0 -toc
GNU xorriso 1.5.3 : RockRidge filesystem manipulator, libburnia
project.

libburn : SORRY : Timeout exceed (30000 ms). Retry canceled.

libburn : SORRY : Command: READ DISC INFORMATION #63,[2 04 00] : 51 00
00 00 00 00 00 00 22 00 : dxfer_len= 34
xorriso : NOTE : Disc status unsuitable for writing
Drive current: -outdev '/dev/sr0'
Media current: is not recognizable
Media status : is not recognizable

xorriso : NOTE : Tolerated problem event of severity 'SORRY'
Drive current: -outdev '/dev/sr0'
Drive access : exclusive:unrestricted
Drive type : vendor 'HL-DT-ST' product 'DVDRAM GH20NS10' revision
'EL00'
Drive id : 'K1386NK4932 '
Media current: is not recognizable
Media status : is not recognizable

Media blocks : 0 readable , 0 writable , 0 overall
TOC layout : Idx , sbsector , Size , Volume Id
xorriso : SORRY : Cannot obtain Table Of Content
xorriso : NOTE : Tolerated problem event of severity 'SORRY'
xorriso : NOTE : -return_with SORRY 32 triggered by problem severity
SORRY

Regards
Chris

On Thu, 2020-09-24 at 16:09 +0000, Thomas Schmitt wrote:
> Hi,
>
> > libburn : SORRY : Asynchronous SCSI error on waiting after START
> > UNIT
> > (+ LOAD) [6 28 81] Drive event. Unknown ASCQ with drive event ASC
> > 28.
>
> Grr. A higher level intervened.
>
> In line 198 of file
>
> ~/xorriso/xorriso-1.5.3/libburn/spc.c
>
> there is
>
> if (key == 0x6 && asc == 0x28 && ascq ==
> 0x00)
>
> which should be shortened to
>
> if (key == 0x6 && asc == 0x28)
>
> Do you feel apt to make this code change and then run
>
> make
>
> again ?
> (Else i would upload a new tarball.)
>
> This time i simulated the drive reply 0x6, 0x28, 0x81 in the waiting
> loop
> from where the message stems. Without " && ascq == 0x00" in line 198
> it
> works for me. So now it is up to your drive to tell me where else
> this
> unexpected error code creates mistrust, or what other interesting
> replies
> it has to offer.
>
> Have a nice day :)
>
> Thomas
>