Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Question
is if above is actually complete growisofs command line?
It comes out of a wrapper script that converts
cdrecord options into runs of dvd+rw-tools.
The write command is supposed to be:
growisofs \
-use-the-force-luke \
-use-the-force-luke=bufsize:16m \
-use-the-force-luke=noload \
-Z /dev/...=/dev/fd/0
Eventually there is also option
speed=...
Then it's very strange...
Point is that growisofs does *not* set layer break,
if you don't pass -dvd-compat [or -dvd-video]
Hmm. That would also make questionable my
argumentation about Problem 2.
No, not at all.
So if growisofs did not issue a layer break position
then Gregoire's drive may or may not have Problem 1.
But in Gregoire's scripts i do read -dvd-compat.
Right...
So probably the theory about number 2 still stands.
But in either case problem 2 is about WRITE command crossing layer break
position. As far as I understand it doesn't matter where is is, default
or explicitly set [to lower value].
As for scdbackup:
I am quite sure that the failed growisofs run
for scdbackup was not with -dvd-compat or any other
option which causes a fixed size. The growisofs
wrapper works fine for sequential DVD-RW where
such a setting would cause the same error.
Not necessarily. The only case that would cause the same error is if
minimally blanked DVD-RW so that DAO gets engaged or DAO is explicitly
engaged on command line. If DVD-RW media is fully blanked or formatted
for restricted overwrite, the you will not suffer from this problem
(unless of course image really fills the media till the very edge, so
there is not place for your additional data).
Obvious is the relation of error position, error
message and size of the plain ISO image.
Regrettably i cannot get that user to make more
experiments which each eat up one DL media.
The problem will have to wait for the next occasion
to show up.
As usual collect versioning information, dvd+rw-mediainfo for resulting
recording, exact command line and exact output. A.
Reply to: