thanx for your quick reply
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
[23315.697128] brasero[9154]: segfault at 2f400 ip 00007fb6350a5231 sp
00007fff0e805918 error 4 in libc-2.32.so[7fb634f6c000+149000]
[23315.697136] Code: 84 00 00 00 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e
0f 1f 84 00 00 00 00 00 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77
1f <c5> fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1
=====================================================
xorriso tells me only
=====================================================
root@darkstar:~# xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee
-i /tmp/xorriso.log
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.
TEST UNIT READY
00 00 00 00 00 00
19 us [ 1091 ]
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
libburn : FAILURE : SCSI command 12h yielded host problem: 0x4
SG_ERR_DID_BAD_TARGET (Bad target, device not responding ?)
libburn : FAILURE : Command: INQUIRY : 12 00 00 00 24 00 : dxfer_len= 36
libburn : FATAL : Lost connection to drive
xorriso : FAILURE : Cannot acquire drive '/dev/sr0'
xorriso : aborting : -abort_on 'FAILURE' encountered 'FATAL'
=====================================================
Il 07/11/21 19:37, Thomas Schmitt ha scritto:
Hi,
i am upstream programmer of libburn, which might be in charge of
burning underneath Brasero. Regrettably i cannot interpret Brasero's
messages unless they come from libburn or libisofs. So i am not sure
whether i can help with fixing Brasero.
The statement by other software that no medium is found in /dev/sr0
surprises me. Such a status assessment is usually done by the drive
and i am not aware of any regular means to let a drive ignore or deny
its loaded medium.
Do you see anything in dmesg that occured when Brasero failed and looks
related to "sr" or "cdrom" ?
Can i talk you into inquring the drive by xorriso and logging its
SCSI transactions when the drive has gone mad from Brasero and a medium
is still inserted ?
xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee -i /tmp/xorriso.log
This would give insight into what the drive tells about its status
without the programs-in-the-middle. The log is quite verbose and will
have several hundred lines. Please post /tmp/xorriso.log as attachment
or send it to me by private mail.
(I wonder why udevadm monitor of Testing is so eager to insert blanks
everywhere. But that would be a different bug, if it is not a copy+paste
artefact.)
Have a nice day :)
Thomas
--
Prof. Mauro Sacchetto
Santa Croce 1332a
30135 Venezia
tel.: 041 722938
cell.: 348 9690575
e-mail:mauro.sacche...@gmail.com
Linux user no.: 353546
public key athttp://keyserver.linux.it
