Comment 15 for bug 397412

Thomas Schmitt (scdbackup) wrote :

Hi,

the initial error report of 2009 is probably due to a hardware problem
in the computers bus controller, or the cabling, or the drive's bus
controller.

> BraseroWodim stderr: CDB: 2A 00 00 01 6C 7E 00 00 1F 00
> ...
> BraseroWodim stderr: Sense Key: 0x0 No Additional Sense, Segment 11
> ...
> BraseroWodim stderr: Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
> ...
> BraseroWodim stderr: Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0

wodim reported the error wrongly, because it does not recognize the error
message format, which is not supposed to be issued by a CD drive.

The error codes are rather: Key= 0xB, ASC= 0, ASCQ= 0.
This means "Command aborted". I.e. Linux decided to abort the WRITE
transaction to block 0x16C7E = 93310. No reason given. (Maybe in dmesg ?)

One can find several reports about this error message and its
misinterpretation by cdrecord, wodim, or growisofs.

Whatever, the error is neither the fault of Brasero nor of the burn program
wodim.

---------------------------------------------------------------------------

> https://ubuntuforums.org/showthread.php?p=7493563

The drive reports that it is not ready to write to block 0x256B = 9579.
That's a drive internal problem.

---------------------------------------------------------------------------

> https://ubuntuforums.org/showthread.php?t=1197582

This is simply a Medium Error, i.e. a problem between drive and medium.
No software on the Linux side of the cable is to blame.

---------------------------------------------------------------------------

> https://lists.ubuntu.com/archives/ubuntu-users/2009-April/179336.html

Totally unrelated.

---------------------------------------------------------------------------

> https://answers.launchpad.net/ubuntu/+source/brasero/+question/76444

The drive reports that it is not ready to write to block 0x1F9B = 8091.
About the same problem as in
  https://ubuntuforums.org/showthread.php?p=7493563

---------------------------------------------------------------------------

> BraseroCDRecord stderr: cdrecord: Input/output error. write_g1: scsi sendcmd: no error

That's what cdrecord and wodim say when they get Key=0xB in the unexpected
error reply format.

---------------------------------------------------------------------------

> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/397412/comments/10
>
> BraseroWodim stderr: Sense Key: 0x4 Hardware Error, deferred error, Segment 0
> ...
> BraseroWodim stderr: Sense Code: 0x09 Qual 0x00 (track following error) Fru

This is a problem between drive and medium, reported in the expected format.

---------------------------------------------------------------------------

> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/397412/comments/11/+download
>
> BraseroCDRecord stderr: Sense Key: 0x5 Illegal Request, Segment 0
> ...
> BraseroCDRecord stderr: Sense Code: 0x30 Qual 0x05 (cannot write medium - incompatible format) Fru 0x0

The drive did not like the mediumi state. Maybe it was already written.

---------------------------------------------------------------------------
Finally the report of today:

> https://launchpadlibrarian.net/331859195/brasero-session.log
>
> BraseroCDRecord stderr: Sense Key: 0x3 Medium Error, Segment 0
> ...
> BraseroCDRecord stderr: Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0

The drive perceived an error when trying to write to the medium.
Block address was 0xFFFFFF6A = -150.
Strange as it is, -150 is the normal start address for a CD SAO run.
So no fault of the burn program.

---------------------------------------------------------------------------

So these bug reports are all about poorly working busses, drives, or media.
Not a single software bug in userland is to see.

Else i would advise to try the libburn backend of Brasero.
But in the cases reported here, success could only happen by incident
when the busses, drives, and media are in better mood.

Have a nice day :)

Thomas