growisofs bug

Bug #1598868 reported by Robert DuPont
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dvd+rw-tools (Ubuntu)
New
Undecided
Unassigned

Bug Description

I am using K3b to burn data DVD's. I have been using the program for years with no problems. But now, the program will not burn data DVk3bD's. It claims to be 'flushing the cache' which I have never seen before. it then cancels without writing anything.

Here is the debugging report:

Burned media
-----------------------
DVD+R

Devices
-----------------------
ASUS SDRW-08D1S-U 1.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]

K3b::IsoImager
-----------------------
mkisofs print size result: 789478 (1616850944 bytes)

System
-----------------------
K3b Version: 2.0.2
KDE Version: 4.13.3
QT Version: 4.8.6
Kernel: 3.19.0-64-generic

Used versions
-----------------------
mkisofs: 1.1.11
growisofs: 7.1

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
/dev/sr0: "Current Write Speed" is 8.2x1352KBps.
:-[ WRITE@LBA=220h failed with SK=3h/WRITE ERROR]: Input/output error
:-( write failed: Input/output error
/dev/sr0: flushing cache

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:789478 -speed=8 -use-the-force-luke=bufsize:32m

mkisofs
-----------------------
789478
I: -input-charset not specified, using utf-8 (detected in locale settings)
  0.06% done, estimate finish Mon Jul 4 10:22:18 2016
  0.13% done, estimate finish Mon Jul 4 10:22:18 2016
  0.19% done, estimate finish Mon Jul 4 10:22:18 2016
  0.25% done, estimate finish Mon Jul 4 10:22:18 2016
  0.32% done, estimate finish Mon Jul 4 10:22:18 2016
  0.38% done, estimate finish Mon Jul 4 10:22:18 2016
  0.44% done, estimate finish Mon Jul 4 10:22:18 2016
  0.51% done, estimate finish Mon Jul 4 10:22:18 2016
  0.57% done, estimate finish Mon Jul 4 10:22:18 2016
  0.63% done, estimate finish Mon Jul 4 10:22:18 2016
  0.70% done, estimate finish Mon Jul 4 10:22:18 2016
  0.76% done, estimate finish Mon Jul 4 10:22:18 2016
  0.82% done, estimate finish Mon Jul 4 10:22:18 2016
  0.89% done, estimate finish Mon Jul 4 10:22:18 2016
  0.95% done, estimate finish Mon Jul 4 10:22:18 2016
  1.01% done, estimate finish Mon Jul 4 10:22:18 2016
  1.08% done, estimate finish Mon Jul 4 10:23:50 2016
  1.14% done, estimate finish Mon Jul 4 10:23:45 2016
  1.20% done, estimate finish Mon Jul 4 10:23:41 2016
  1.27% done, estimate finish Mon Jul 4 10:23:36 2016
  1.33% done, estimate finish Mon Jul 4 10:23:33 2016
  1.39% done, estimate finish Mon Jul 4 10:23:29 2016
  1.46% done, estimate finish Mon Jul 4 10:23:26 2016
  1.52% done, estimate finish Mon Jul 4 10:23:23 2016
  1.58% done, estimate finish Mon Jul 4 10:23:21 2016
  1.65% done, estimate finish Mon Jul 4 10:23:18 2016
  1.71% done, estimate finish Mon Jul 4 10:23:16 2016
  1.77% done, estimate finish Mon Jul 4 10:23:14 2016
  1.84% done, estimate finish Mon Jul 4 10:23:12 2016
  1.90% done, estimate finish Mon Jul 4 10:23:10 2016
  1.96% done, estimate finish Mon Jul 4 10:23:08 2016
  2.03% done, estimate finish Mon Jul 4 10:23:07 2016
  2.09% done, estimate finish Mon Jul 4 10:23:05 2016

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid K3b data project -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-robert/k3bcF2851.tmp -rational-rock -hide-list /tmp/kde-robert/k3bcS2851.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-robert/k3bVs2851.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-robert/k3baq2851.tmp

mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid K3b data project -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-robert/k3bGS2851.tmp -rational-rock -hide-list /tmp/kde-robert/k3btQ2851.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-robert/k3bmn2851.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-robert/k3bbh2851.tmp

I believe the problem lies in the growisofs program, for I have tried other burning programs and the same thing occurs

Revision history for this message
Thomas Schmitt (scdbackup) wrote :

Hi,

> growisofs
> ...
> :-[ WRITE@LBA=220h failed with SK=3h/WRITE ERROR]: Input/output error

Regrettably it does not tell the additional info numbers ASC and ASCQ.
But SK=3 means that the drive cannot write to the medium because of
unexpected problems. I.e. not because the DVD would not be writable by
its type and state.

"220h" means that the drive raised protest after growisofs sent it the
first 544 blocks = 1,114,112 bytes. This is well within the size of the
drive buffer. So one may assume that the drive was not able to write
any data with sufficient quality.

If other burn programs (e.g. my libburn) yield better success, then this
would either be because mere luck, or because a different write method was
used. Write methods depend on the DVD type, e.g. DVD-R offers DAO and
Incremental, DVD+R offers writing with or without track reservation.
The growisofs run did not require DAO. But it is not obvious whether DVD-R
or DVD+R was in use.

Whatever, a first try of remedy would be to buy some new DVD media of
the other type as the one used before. E.g. DVD-R if your failure was with
DVD+R. If this helps, try newly bought DVD of the type and manufacturer
that failed before.

If not the failing old DVD media turn out to be just bad while all newly
bought DVD work fine, then it is time to consider replacing the burner drive.

Have a nice day :)

Thomas

Revision history for this message
Robert DuPont (omnipop1026) wrote : Re: [Bug 1598868] Re: growisofs bug
Download full text (7.0 KiB)

Hello,

Thanks for your prompt response and analysis.

I will try getting some DVD-R instead of +R and see if that works.
The burner is about eight years old, it has been great, maybe it's finally
giving out.

Thank you again

RFD
On Jul 5, 2016 6:35 AM, "Thomas Schmitt" <email address hidden> wrote:

> Hi,
>
> > growisofs
> > ...
> > :-[ WRITE@LBA=220h failed with SK=3h/WRITE ERROR]: Input/output error
>
> Regrettably it does not tell the additional info numbers ASC and ASCQ.
> But SK=3 means that the drive cannot write to the medium because of
> unexpected problems. I.e. not because the DVD would not be writable by
> its type and state.
>
> "220h" means that the drive raised protest after growisofs sent it the
> first 544 blocks = 1,114,112 bytes. This is well within the size of the
> drive buffer. So one may assume that the drive was not able to write
> any data with sufficient quality.
>
> If other burn programs (e.g. my libburn) yield better success, then this
> would either be because mere luck, or because a different write method was
> used. Write methods depend on the DVD type, e.g. DVD-R offers DAO and
> Incremental, DVD+R offers writing with or without track reservation.
> The growisofs run did not require DAO. But it is not obvious whether DVD-R
> or DVD+R was in use.
>
> Whatever, a first try of remedy would be to buy some new DVD media of
> the other type as the one used before. E.g. DVD-R if your failure was with
> DVD+R. If this helps, try newly bought DVD of the type and manufacturer
> that failed before.
>
> If not the failing old DVD media turn out to be just bad while all newly
> bought DVD work fine, then it is time to consider replacing the burner
> drive.
>
> Have a nice day :)
>
> Thomas
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1598868
>
> Title:
> growisofs bug
>
> Status in dvd+rw-tools package in Ubuntu:
> New
>
> Bug description:
> I am using K3b to burn data DVD's. I have been using the program for
> years with no problems. But now, the program will not burn data
> DVk3bD's. It claims to be 'flushing the cache' which I have never seen
> before. it then cancels without writing anything.
>
> Here is the debugging report:
>
> Burned media
> -----------------------
> DVD+R
>
> Devices
> -----------------------
> ASUS SDRW-08D1S-U 1.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R,
> DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential,
> DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW
> Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer,
> CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P,
> RAW/R96R, Restricted Overwrite, Layer Jump] [%7]
>
> K3b::IsoImager
> -----------------------
> mkisofs print size result: 789478 (1616850944 bytes)
>
> System
> -----------------------
> K3b Version: 2.0.2
> KDE Version: 4.13.3
> QT Version: 4.8.6
> Kernel: 3.19.0-64-generic
>
> Used versions
> -----------------------
> mkisofs: 1.1.11
> growisofs: 7.1
>
> growisofs
> -----------------------
> Executing ...

Read more...

Revision history for this message
Robert DuPont (omnipop1026) wrote :
Download full text (5.3 KiB)

I tried it again , this time using DVD - R and the growisofs crashed again.

Here is the report:

Burned media
-----------------------
DVD-R Sequential

Devices
-----------------------
ASUS SDRW-08D1S-U 1.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]

K3b::IsoImager
-----------------------
mkisofs print size result: 2255045 (4618332160 bytes)

System
-----------------------
K3b Version: 2.0.2
KDE Version: 4.13.3
QT Version: 4.8.6
Kernel: 3.19.0-64-generic

Used versions
-----------------------
mkisofs: 1.1.11
growisofs: 7.1

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
/dev/sr0: "Current Write Speed" is 8.2x1352KBps.
          0/4618332160 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU 0.0%
=== last message repeated 2 times. ===
:-[ WRITE@LBA=10h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument
:-( write failed: Invalid argument
/dev/sr0: flushing cache
/dev/sr0: updating RMA
/dev/sr0: closing disc

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:2255045 -dvd-compat -speed=8 -use-the-force-luke=bufsize:32m

mkisofs
-----------------------
2255045
I: -input-charset not specified, using utf-8 (detected in locale settings)
Using FRED_ASTAIRE___THE_EARLY_YEA000 for /Fred Astaire - The Early Years at RKO - Disc 1 (Fred Astaire - The Early Years At RKO - Disc 2)
Using ELVIS_COSTELLO___UNFAITHFUL_000 for /Elvis Costello - Unfaithful Music & Soundtrack Album (disc 2) (Elvis Costello - Unfaithful Music & Soundtrack Album (disc 1))
Using BOB_DYLAN___THE_BEST_OF_THE_000 for /Bob Dylan - The Best of The Cutting Edge 1965–1966: The Bootleg Series, Vol. 12 (disc 2) (Bob Dylan - The Best of The Cutting Edge 1965–1966: The Bootleg Series, Vol. 12 (disc 1))
  0.02% done, estimate finish Sat Jul 9 09:55:23 2016
  0.04% done, estimate finish Sat Jul 9 09:55:23 2016
  0.07% done, estimate finish Sat Jul 9 09:55:23 2016
  0.09% done, estimate finish Sat Jul 9 09:55:23 2016
  0.11% done, estimate finish Sat Jul 9 09:55:23 2016
  0.13% done, estimate finish Sat Jul 9 09:55:23 2016
  0.16% done, estimate finish Sat Jul 9 09:55:23 2016
  0.18% done, estimate finish Sat Jul 9 10:04:45 2016
  0.20% done, estimate finish Sat Jul 9 10:03:43 2016
  0.22% done, estimate finish Sat Jul 9 10:02:53 2016
  0.24% done, estimate finish Sat Jul 9 10:02:12 2016
  0.27% done, estimate finish Sat Jul 9 10:01:38 2016
  0.29% done, estimate finish Sat Jul 9 10:01:09 2016
  0.31% done, estimate finish Sat Jul 9 10:00:45 2016
  0.33% done, estimate finish Sat Jul 9 10:00:23 2016
  0.36% done, estimate finish Sat Jul 9 10:00:04 2016
  0.38% done, estimate finish Sat Jul 9 09:59:48 2016
  0.40% done, estimate finish Sat Jul...

Read more...

Revision history for this message
Thomas Schmitt (scdbackup) wrote :

Hi,

growisofs wrote:
> :-[ WRITE@LBA=10h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument

LBA=10h means that the second WRITE command yielded a failure message
from the drive. The accusation is strange.

I have seen this only with cdrecord yet, when the Linux kernel reported
(falsely) to cdrecord that the bytes of the previous WRITE command had
not been transmitted. cdrecord then repeated the WRITE command and got
above error reply.

Looking at the code of function poor_mans_pwrite64() in growisofs_mmc.cpp
  https://sources.debian.net/src/dvd%2Brw-tools/7.1-11/growisofs_mmc.cpp/#L466
it seems that growisofs repeats WRITE commands only when the drive invites
this by one of two "NOT READY" replies: "LONG WRITE IN PROGRESS" and
"IN PROCESS OF BECOMING READY".

Whatever, this behavior is not normal.

> followed by 'updating RMA' (this is new),

RMA means "Recording Management Area". This is on DVD-R what Table-of-Content
is on CD-R. It records the structure of sessions and tracks.

growisofs says "updating RMA" before it issues the CLOSE TRACK/SESSION
command at the end of a DVD-R run with write type "Incremental".
  https://sources.debian.net/src/dvd%2Brw-tools/7.1-11/growisofs_mmc.cpp/#L1908

If you can talk K3B into using write type "DAO" (aka "Disc-at-Once"),
then this might be worth a try.
Given the endurance with failure, i have few hope for success, though.

> Again the burner and k3b
> work fine doing other functions , like burning regular CD's

Afaik, the lasers for CD and DVD are different devices inside the burner.
(I recently had the case that a Blu-ray burner lost its sight for BD media
but not for DVD or CD.)

Have a nice day :)

Thomas

Revision history for this message
Robert DuPont (omnipop1026) wrote :
Download full text (7.3 KiB)

Thanks again for the info. I will try the DAO function and is that doesn't
work, it must be the burner. I've had it for years, but it's probably
crapping out. Thanks again.

RFD
On Jul 9, 2016 12:15 PM, "Thomas Schmitt" <email address hidden> wrote:

> Hi,
>
> growisofs wrote:
> > :-[ WRITE@LBA=10h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid
> argument
>
> LBA=10h means that the second WRITE command yielded a failure message
> from the drive. The accusation is strange.
>
> I have seen this only with cdrecord yet, when the Linux kernel reported
> (falsely) to cdrecord that the bytes of the previous WRITE command had
> not been transmitted. cdrecord then repeated the WRITE command and got
> above error reply.
>
> Looking at the code of function poor_mans_pwrite64() in growisofs_mmc.cpp
>
> https://sources.debian.net/src/dvd%2Brw-tools/7.1-11/growisofs_mmc.cpp/#L466
> it seems that growisofs repeats WRITE commands only when the drive invites
> this by one of two "NOT READY" replies: "LONG WRITE IN PROGRESS" and
> "IN PROCESS OF BECOMING READY".
>
> Whatever, this behavior is not normal.
>
>
> > followed by 'updating RMA' (this is new),
>
> RMA means "Recording Management Area". This is on DVD-R what
> Table-of-Content
> is on CD-R. It records the structure of sessions and tracks.
>
> growisofs says "updating RMA" before it issues the CLOSE TRACK/SESSION
> command at the end of a DVD-R run with write type "Incremental".
>
> https://sources.debian.net/src/dvd%2Brw-tools/7.1-11/growisofs_mmc.cpp/#L1908
>
> If you can talk K3B into using write type "DAO" (aka "Disc-at-Once"),
> then this might be worth a try.
> Given the endurance with failure, i have few hope for success, though.
>
>
> > Again the burner and k3b
> > work fine doing other functions , like burning regular CD's
>
> Afaik, the lasers for CD and DVD are different devices inside the burner.
> (I recently had the case that a Blu-ray burner lost its sight for BD media
> but not for DVD or CD.)
>
>
> Have a nice day :)
>
> Thomas
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1598868
>
> Title:
> growisofs bug
>
> Status in dvd+rw-tools package in Ubuntu:
> New
>
> Bug description:
> I am using K3b to burn data DVD's. I have been using the program for
> years with no problems. But now, the program will not burn data
> DVk3bD's. It claims to be 'flushing the cache' which I have never seen
> before. it then cancels without writing anything.
>
> Here is the debugging report:
>
> Burned media
> -----------------------
> DVD+R
>
> Devices
> -----------------------
> ASUS SDRW-08D1S-U 1.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R,
> DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential,
> DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW
> Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer,
> CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P,
> RAW/R96R, Restricted Overwrite, Layer Jump] [%7]
>
> K3b::IsoImager
> -----------------------
> mkisofs print size result: 789478 (1616850944 bytes)
>
> ...

Read more...

Revision history for this message
soyka (stefan-soyka) wrote :

I burnt one DVD+R fine, the second failed (using k3b). After the failure the media displayed like:

Media current: DVD+R
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free
Drive current: -outdev '/dev/sr0'
Drive type : vendor 'HL-DT-ST' product 'DVDRAM GH22NS40' revision 'NL00'
Drive id : 'K0I8AQ00232 '
Media current: DVD+R
Media product: RITEK/F16/49 , Ritek Corp
Media status : is blank
Media blocks : 0 readable , 2295104 writable , 2295104 overall
Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free

I tried four more media from the same batch, to no avail.

As it appeared to be media/burner-problem, I shut down the pc and started again, that did the trick.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.