Bug#998718: Brasero fails (on Testing) burning an ISO image on a CD-RW

[Thomas Schmitt]

Hi,

(No need to Cc: me, i am subscribed to the bug report 998718.
If you are subscribed too and don't want to be Cc:ed, then tell me.)

> thanx for your quick reply

That's because new udevadm said "XORRISO". I found the bug report by my
evening patrol with Google.

-----------------------------------------------------------------------
Diagnosis:

The unusable drive state looks like a bad relationship between drive
and kernel. Regrettably the dmesg log does not tell how Brasero brought
this relationship in its bad shape.

------------------------------------------------------------------------
What to do next:

Did you already try what happens if you eject the CD and insert it again
after spoiling the drive state with Brasero and before using the drive
for mounting or for xorriso -toc ?
If not yet, then please do.

> xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

I guess this means you are running Debian "testing".
("stable" has version 1.5.2.)

To outrule the possibility that libburn underneath Brasero is to blame,
please use xorriso to burn an image by this drive:

  isoimage=...path.to.your.ISO.image.file...

  xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed $isoimage

Then try whether the drive is still usable.
(Crossing fingers now.)

---------------------------------------------------------------------
Just in case somebody is interested in details of my diagnosis:

Mauro Sacchetto wrote:
> dmesg tell me:
> [23315.697087] sr 5:0:0:0: [sr0] tag#16 FAILED Result:
> hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
> [23315.697092] sr 5:0:0:0: [sr0] tag#16 CDB: Prevent/Allow Medium Removal 1e
> 00 00 00 01 00

The drive did not respond to a SCSI command from the kernel's SCSI
driver. Brasero obviously tried to lock the drive tray so that pressing
the eject button would have no effect. (At least with motorized trays.)

> [23315.697128] brasero[9154]: segfault at 2f400 ip 00007fb6350a5231 sp
> 00007fff0e805918 error 4 in libc-2.32.so[7fb634f6c000+149000]

This might be due to a bug in Brasero, which would not react properly
on the failure of the tray locking attempt.


> xorriso tells me only
> TEST UNIT READY
> 00 00 00 00 00 00
>       19 us     [ 1091 ]

The drive obviously responded to this SCSI command (indicating that it
is ready for work).


> INQUIRY
> 12 00 00 00 24 00
> From drive: 36b
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>        10 us     [ 1207 ]
> --- SG_IO: host_status= 0x4 SG_ERR_DID_BAD_TARGET (Bad target, device not
> responding ?)
> --- SG_IO: Gave up connection to drive

Here the drive did not respond to the kernel, which thus reported the
DID_BAD_TARGET to libburn. The Linux SG_IO adapter of libburn then gave
up the connection.

> libburn : FATAL : Lost connection to drive
> xorriso : FAILURE : Cannot acquire drive '/dev/sr0'
> xorriso : aborting : -abort_on 'FAILURE' encountered 'FATAL'

But xorriso at least found a way out without producing a segmentation
fault in libc or elsewhere.


> Better than my previous report:
> xorriso -scsi_log on -outdev /dev/sr0 -toc
> [... longer list of SCSI transactions ...]
> Media current: CD-RW
> [...]
> Media product: 97m26s65f/79m59s74f , CMC Magnetics Corporation
> Media status : is written , is closed
> [...]
> TOC layout   : Idx ,  sbsector ,       Size , Volume Id
> ISO session  :   1 ,         0 ,    193536s , Debian 11.1.0 amd64 n
> Media summary: 1 session, 193536 data blocks,  378m data,     0 free

All seems well. The drive responds to commands in reasonable time,
the medium is recognized as CD-RW, and the filesystem is recognized
as ISO 9660.


Have a nice day :)

Thomas