Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"

apport information

apport information

Hi,

the error message stems from the burner drive and was forwarded by libburn
to Brasero. Strangely the code ASC=21 , ASCQ=04 is not specified in in
the SCSI specs for optical drives (MMC).
In the overall error code list
  https://www.t10.org/lists/asc-num.htm
it is listed for other device classes as
  21h/04h DZ UNALIGNED WRITE COMMAND

I know this error code from
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718
with
  Drive type : vendor 'ASUS' product 'DRW-24D5MT' revision '2.00'
Brasero crashed at that occasion before it could start to write.
The indirect reason seems to be a bad READ CD command which Brasero
emitted on its own (i.e. not via libburn). It brings the firmware of
two ASUS drives to a state from where it throws that error code.
(Mine is a BW-16D1HT with firmware 1.01.)
It happens only with CD media which were written by write type TAO.

So (assuming that the drive has address /dev/sr0):

- What is the vendor, model, revision of your drive.
  You may obtain it from the empty drive by

    xorriso -outdev /dev/sr0 -toc | grep 'Drive type'

- Do you experience the problem with CD-R or CD-RW media ?
  If so:

  - What happens if you use a writable DVD medium instead ?

  - Does it help to blank the CD medium before using it with Brasero:

      xorriso -outdev /dev/sr0 -blank as_needed

- Do you experience the problem with other GUI programs like K3B or
  Xfburn ?

- Do you experience the problem with a run of xorriso ?

    ISO="...path.to.your.iso.image.file..."
    xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO"

Have a nice day :)

Thomas

Hi Thomas;

Thank you very much for getting back to me. So will try to answer your
questions. Some of which may be delayed due to me having to run test.

*- What is the vendor, model, revision of your drive. You may obtain it
from the empty drive by*

xorriso : NOTE : Disc status unsuitable for writing
Drive current: -outdev '/dev/sr0'
Media current: is not recognizable
Media status : is not present
Drive type : vendor 'ASUS' product 'BW-16D1HT' revision '3.10'

*- Do you experience the problem with CD-R or CD-RW media ? If so:*

* - What happens if you use a writable DVD medium instead ?*

* - Does it help to blank the CD medium before using it with Brasero:*
* xorriso -outdev /dev/sr0 -blank as_needed*

Will Run these test shortly and get back to you with the results

*- Do you experience the problem with other GUI programs like K3B or
Xfburn ? - Do you experience the problem with a run of xorriso ?
ISO="...path.to.your.iso.image.file..." xorriso -as cdrecord -v
dev=/dev/sr0 blank=as_needed "$ISO"*

Have not tried K3B or Xfburn. Did try Nero for Linux and had the same
result as I did with Brasero.

Thank you very much for the assistance. Talk shortly.

On Fri, Mar 11, 2022 at 3:10 AM Thomas Schmitt <email address hidden>
wrote:

> Hi,
>
> the error message stems from the burner drive and was forwarded by libburn
> to Brasero. Strangely the code ASC=21 , ASCQ=04 is not specified in in
> the SCSI specs for optical drives (MMC).
> In the overall error code list
> https://www.t10.org/lists/asc-num.htm
> it is listed for other device classes as
> 21h/04h DZ UNALIGNED WRITE COMMAND
>
> I know this error code from
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718
> with
> Drive type : vendor 'ASUS' product 'DRW-24D5MT' revision '2.00'
> Brasero crashed at that occasion before it could start to write.
> The indirect reason seems to be a bad READ CD command which Brasero
> emitted on its own (i.e. not via libburn). It brings the firmware of
> two ASUS drives to a state from where it throws that error code.
> (Mine is a BW-16D1HT with firmware 1.01.)
> It happens only with CD media which were written by write type TAO.
>
> So (assuming that the drive has address /dev/sr0):
>
> - What is the vendor, model, revision of your drive.
> You may obtain it from the empty drive by
>
> xorriso -outdev /dev/sr0 -toc | grep 'Drive type'
>
> - Do you experience the problem with CD-R or CD-RW media ?
> If so:
>
> - What happens if you use a writable DVD medium instead ?
>
> - Does it help to blank the CD medium before using it with Brasero:
>
> xorriso -outdev /dev/sr0 -blank as_needed
>
> - Do you experience the problem with other GUI programs like K3B or
> Xfburn ?
>
> - Do you experience the problem with a run of xorriso ?
>
> ISO="...path.to.your.iso.image.file..."
> xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO"
>
>
> Have a nice day :)
>
> Thomas
>
>
> ** Bug watch added: Debian Bug tracker #998718
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718
>
> --
> You received this bug notification because you are subscribed to the bug
> repor...

Hi,

C. Clear wrote:
> Drive type : vendor 'ASUS' product 'BW-16D1HT' revision '3.10'

That would match the Debian bug of last year.

> Did try Nero for Linux and had the same
> result as I did with Brasero.

Keep in mind that in the Debian bug scenario Brasero's bad read attempt
spoiled the two ASUS drives until they got a power-off-on cycle. If the
drive is built into the computer this means a power-off-on cycle of the
computer, i fear. (I have mine in a USB box. That eases the problem.)

It was enough to show Brasero a CD burnt with wite type TAO to let the
drive go mad. It was not necessary to make a burn attempt.
The only workaround was to blank CD-RW by other programs before giving
them to Brasero for being re-written.

Unfortunately TAO is the write type used by Brasero itself. Other programs
may choose SAO with the consequence that those CDs don't let the drive go
mad, even when they get shown to Brasero.

Have a nice day :)

Thomas

Thanks for getting back to me. So a question to ask

*Brasero's bad read attempt spoiled the two ASUS drives until they got a
power-off-on cycle. If the drive is built into the computer this means a
power-off-on cycle of the computer, i fear*

What does doing a power off/on cycle entail ??? Disconnecting the Drive and
computer from power and replugging it in or something more complex ??

On Sat, Mar 12, 2022 at 5:30 PM Thomas Schmitt <email address hidden>
wrote:

> Hi,
>
> C. Clear wrote:
> > Drive type : vendor 'ASUS' product 'BW-16D1HT' revision '3.10'
>
> That would match the Debian bug of last year.
>
>
> > Did try Nero for Linux and had the same
> > result as I did with Brasero.
>
> Keep in mind that in the Debian bug scenario Brasero's bad read attempt
> spoiled the two ASUS drives until they got a power-off-on cycle. If the
> drive is built into the computer this means a power-off-on cycle of the
> computer, i fear. (I have mine in a USB box. That eases the problem.)
>
> It was enough to show Brasero a CD burnt with wite type TAO to let the
> drive go mad. It was not necessary to make a burn attempt.
> The only workaround was to blank CD-RW by other programs before giving
> them to Brasero for being re-written.
>
> Unfortunately TAO is the write type used by Brasero itself. Other programs
> may choose SAO with the consequence that those CDs don't let the drive go
> mad, even when they get shown to Brasero.
>
>
> Have a nice day :)
>
> Thomas
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1964554
>
> Title:
> Brasero does not burn ISO IMAGE. Error message; "SCSI error on
> write(0,16): See MMC specs: Sense Key 5 "Illegal request"
>
> Status in brasero package in Ubuntu:
> New
>
> Bug description:
>
> BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC
> specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
> BraseroLibburn called brasero_job_set_current_action
> BraseroLibburn Libburn reported an error SCSI error on write(0,16): See
> MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
> BraseroLibburn called brasero_job_error
> BraseroLibburn finished with an error
> BraseroLibburn asked to stop because of an error
> error = 1
> message = "SCSI error on write(0,16): See MMC specs: Sense Key 5
> "Illegal request", ASC 21 ASCQ 04."
> BraseroLibburn stopping
> Session error : SCSI error on write(0,16): See MMC specs: Sense Key 5
> "Illegal request", ASC 21 ASCQ 04. (brasero_burn_record brasero-burn.c:2856)
> ---
> ProblemType: Bug
> ApportVersion: 2.20.9-0ubuntu7.27
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> InstallationDate: Installed on 2021-01-31 (403 days ago)
> InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
> (20190805)
> Package: brasero 3.12.1-4ubuntu2
> PackageArchitecture: amd64
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 5.4.0-100.113~18.04.1-generic 5.4....

Hi,

C. Clear wrote:
> What does doing a power off/on cycle entail ???

Just a shutdown so that the burner drive has no electrical power.
If in doubt whether the power is really off, press the drive's eject
button. The drive should not react.

Have a nice day :)

Thomas

Got it.

On Sun, Mar 13, 2022 at 3:40 AM Thomas Schmitt <email address hidden>
wrote:

> Hi,
>
> C. Clear wrote:
> > What does doing a power off/on cycle entail ???
>
> Just a shutdown so that the burner drive has no electrical power.
> If in doubt whether the power is really off, press the drive's eject
> button. The drive should not react.
>
>
> Have a nice day :)
>
> Thomas
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1964554
>
> Title:
> Brasero does not burn ISO IMAGE. Error message; "SCSI error on
> write(0,16): See MMC specs: Sense Key 5 "Illegal request"
>
> Status in brasero package in Ubuntu:
> New
>
> Bug description:
>
> BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC
> specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
> BraseroLibburn called brasero_job_set_current_action
> BraseroLibburn Libburn reported an error SCSI error on write(0,16): See
> MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
> BraseroLibburn called brasero_job_error
> BraseroLibburn finished with an error
> BraseroLibburn asked to stop because of an error
> error = 1
> message = "SCSI error on write(0,16): See MMC specs: Sense Key 5
> "Illegal request", ASC 21 ASCQ 04."
> BraseroLibburn stopping
> Session error : SCSI error on write(0,16): See MMC specs: Sense Key 5
> "Illegal request", ASC 21 ASCQ 04. (brasero_burn_record brasero-burn.c:2856)
> ---
> ProblemType: Bug
> ApportVersion: 2.20.9-0ubuntu7.27
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> InstallationDate: Installed on 2021-01-31 (403 days ago)
> InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
> (20190805)
> Package: brasero 3.12.1-4ubuntu2
> PackageArchitecture: amd64
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 5.4.0-100.113~18.04.1-generic 5.4.166
> Tags: bionic
> Uname: Linux 5.4.0-100-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions
>
>

Ollo;

sorry to take so long to get back to you but I have ran the cd-r test.

*Do you experience the problem with CD-R or CD-RW media ?*

Yes. The exact same error message as when I tried to make a DVD.

*Does it help to blank the CD medium before using it with Brasero:
xorriso -outdev /dev/sr0 -blank as_needed*

Unfortunately No. Tried twice and the same error Message.

Did the Power off/on Cycle and that also had no effect.

Thanks for your help and hoping that some solution comes up.

On Wed, Mar 16, 2022 at 8:24 PM Carl W <email address hidden> wrote:

> Got it.
>
> On Sun, Mar 13, 2022 at 3:40 AM Thomas Schmitt <email address hidden>
> wrote:
>
>> Hi,
>>
>> C. Clear wrote:
>> > What does doing a power off/on cycle entail ???
>>
>> Just a shutdown so that the burner drive has no electrical power.
>> If in doubt whether the power is really off, press the drive's eject
>> button. The drive should not react.
>>
>>
>> Have a nice day :)
>>
>> Thomas
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1964554
>>
>> Title:
>> Brasero does not burn ISO IMAGE. Error message; "SCSI error on
>> write(0,16): See MMC specs: Sense Key 5 "Illegal request"
>>
>> Status in brasero package in Ubuntu:
>> New
>>
>> Bug description:
>>
>> BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC
>> specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
>> BraseroLibburn called brasero_job_set_current_action
>> BraseroLibburn Libburn reported an error SCSI error on write(0,16): See
>> MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
>> BraseroLibburn called brasero_job_error
>> BraseroLibburn finished with an error
>> BraseroLibburn asked to stop because of an error
>> error = 1
>> message = "SCSI error on write(0,16): See MMC specs: Sense Key 5
>> "Illegal request", ASC 21 ASCQ 04."
>> BraseroLibburn stopping
>> Session error : SCSI error on write(0,16): See MMC specs: Sense Key 5
>> "Illegal request", ASC 21 ASCQ 04. (brasero_burn_record brasero-burn.c:2856)
>> ---
>> ProblemType: Bug
>> ApportVersion: 2.20.9-0ubuntu7.27
>> Architecture: amd64
>> CurrentDesktop: ubuntu:GNOME
>> DistroRelease: Ubuntu 18.04
>> InstallationDate: Installed on 2021-01-31 (403 days ago)
>> InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
>> (20190805)
>> Package: brasero 3.12.1-4ubuntu2
>> PackageArchitecture: amd64
>> ProcEnviron:
>> TERM=xterm-256color
>> PATH=(custom, no user)
>> XDG_RUNTIME_DIR=<set>
>> LANG=en_US.UTF-8
>> SHELL=/bin/bash
>> ProcVersionSignature: Ubuntu 5.4.0-100.113~18.04.1-generic 5.4.166
>> Tags: bionic
>> Uname: Linux 5.4.0-100-generic x86_64
>> UpgradeStatus: No upgrade log present (probably fresh install)
>> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>> _MarkForUpload: True
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions
>>
>>

Hi,

> > *Do you experience the problem with CD-R or CD-RW media ?*

> Yes. The exact same error message as when I tried to make a DVD.

Then it is not exactly the same problem as with the DRW-24D5MT of
Mauro Sacchetto and my BW-16D1HT as of Debian bug 998718.

Your Brasero version 3.12.1-4ubuntu2 seems slightly younger than
the 3.12.3-1 of Mauro and the 3.12.2-5 which i tested. But there was
no visible development in Brasero since quite a while. So i would not
blame the difference on the versions ... for now.

> > Does it help to blank the CD medium before using it with Brasero:
> > xorriso -outdev /dev/sr0 -blank as_needed*

> Unfortunately No.

What about other burn programs (with a power-cycle between the last
Brasero run and the the new experiment) ?

Like:

    ISO="...path.to.your.iso.image.file..."
    xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO"

Have a nice day :)

Thomas

Hi Thomas;

Hope you are well and life is being kind.

Forgive the late reply but have been busy with work. So at this point I
have tried these Burn Programs

Brasero
Imgburn
K3b
Brasero

All give back a similar message. I am going to on Boot try a earlier
version of Ubuntu or maybe Safe mode to see if that would be a solution. It
is really difficult to tell wether this is a OS or Hardware issue.

Thank you very much for trying to assist me. Best Regards

On Thu, Mar 17, 2022 at 4:10 AM Thomas Schmitt <email address hidden>
wrote:

> Hi,
>
> > > *Do you experience the problem with CD-R or CD-RW media ?*
>
> > Yes. The exact same error message as when I tried to make a DVD.
>
> Then it is not exactly the same problem as with the DRW-24D5MT of
> Mauro Sacchetto and my BW-16D1HT as of Debian bug 998718.
>
> Your Brasero version 3.12.1-4ubuntu2 seems slightly younger than
> the 3.12.3-1 of Mauro and the 3.12.2-5 which i tested. But there was
> no visible development in Brasero since quite a while. So i would not
> blame the difference on the versions ... for now.
>
>
> > > Does it help to blank the CD medium before using it with Brasero:
> > > xorriso -outdev /dev/sr0 -blank as_needed*
>
> > Unfortunately No.
>
> What about other burn programs (with a power-cycle between the last
> Brasero run and the the new experiment) ?
>
> Like:
>
> ISO="...path.to.your.iso.image.file..."
> xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO"
>
>
> Have a nice day :)
>
> Thomas
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1964554
>
> Title:
> Brasero does not burn ISO IMAGE. Error message; "SCSI error on
> write(0,16): See MMC specs: Sense Key 5 "Illegal request"
>
> Status in brasero package in Ubuntu:
> New
>
> Bug description:
>
> BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC
> specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
> BraseroLibburn called brasero_job_set_current_action
> BraseroLibburn Libburn reported an error SCSI error on write(0,16): See
> MMC specs: Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
> BraseroLibburn called brasero_job_error
> BraseroLibburn finished with an error
> BraseroLibburn asked to stop because of an error
> error = 1
> message = "SCSI error on write(0,16): See MMC specs: Sense Key 5
> "Illegal request", ASC 21 ASCQ 04."
> BraseroLibburn stopping
> Session error : SCSI error on write(0,16): See MMC specs: Sense Key 5
> "Illegal request", ASC 21 ASCQ 04. (brasero_burn_record brasero-burn.c:2856)
> ---
> ProblemType: Bug
> ApportVersion: 2.20.9-0ubuntu7.27
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 18.04
> InstallationDate: Installed on 2021-01-31 (403 days ago)
> InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
> (20190805)
> Package: brasero 3.12.1-4ubuntu2
> PackageArchitecture: amd64
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 5.4.0-100.11...