growisofs bug
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-
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/
mkisofs command:
-------
/usr/bin/
I believe the problem lies in the growisofs program, for I have tried other burning programs and the same thing occurs
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