For the first time ever, I need to burn a dual-layer DVD.

K3B, Brasero and XFBurn all failed to write an ISO image (7.7GB). K3B also failed to write files to a DVD+R DL disc.

So I went to the CLI and tried to use growisofs directly. This is what I got
I am running Debian Sid / Plasma / Linux 4.8.0-2-686-pae #1 SMP Debian 4.8.15-2 (2017-01-04) i686 GNU/Linux

If it matters, the iso file was created from a Japanese Radio/GPS DVD, backing up the existing one.

Any help will be appreciated.

How many blanks did you test and did you try burning data, any data, to this blank from another machine?

It's not unusual to come across the occasional bad blank.

Five blanks, 2 machines (different brand burners) and 2 filesets.

2 of the blanks were "spoiled" in that their capacity was reported as reduced after a 1st attempt. So it looks like a write started then aborted.

BTW, I am using SysV, not SystemD

Hi,

the error message SK=5h/ASC=21h/ACQ=04h is issued by the drive. It means
that the drive did not like the command which was sent to it. In this
case it was a SCSI WRITE10 command which tried to write to block 0.

Hard to imagine what should be wrong with that command. One possible
cause would be that growisofs already sent a previous WRITE command
for the same address. But that is quite unlikely.

Regreattably growisofs does not offer an option to watch its dialog
with the drive.

What do you get from
This will be quite verbous, especially when the burn run succeeds.
Thus the "tee" command and the redirection "2>&1" which put a copy
of the output into file /tmp/xorriso.log . This file would be
interesting to see.

xorriso uses libburn as backend, which is also used by Xfburn.
So we can hardly hope for a miracle success here.


> Five blanks, 2 machines (different brand burners)

That's riddling. growisofs is known to be able to burn DVD+R DL.
But two mad drives are quite unlikely either.


Have a nice day

Thomas

I ran the command you suggested. Result was a 660 line log of a FAILED burn.

Probably the most revealing part is:

What's the best way to send you the full file?

Could it be that the file size is too large? The discs are labelled 8.5Gigabyte but I don't know how much is taken up by overhead.

K3b reports a brand new disc as having a capacity of 8.0 GiB and Brasero reports 8.5.

Thanks

Hi,

> What's the best way to send you the full file?

Mail it to scdbackup@gmx.net if it is too large for the "Manage Attachments"
feature of the "Post Reply" page here.


> libburn : FAILURE : SCSI error condition on command 53h RESERVE TRACK: [3 72 00] Medium error. Session fixation error.
> libburn : FATAL : Cannot reserve track of 8388345856 bytes

This error means that the drive did not like the medium. That's different
from the drive not liking the SCSI command WRITE10.

What do you get from the affected medium aftwerwards by:
If there is a line "Media status : is blank", then the DVD+R DL is still
usable.


A test of the same "xorriso -as cdrecord" command on the other drive would
be interesting. If it too says "Medium error" then we need not to riddle
further. Then it would really be two broken relationships between drives
an media.

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

The failed medium reservation command is not mandatory with DVD+R DL. One
can avoid it by adding option "-tao" to the "xorriso -as cdrecord" run.
Probably we will see an error with a WRITE10 command then.

But if it works by miracle:
Xfburn offers a "Write mode" in the middle of the "Burn image" dialog window.
There is "Auto", "TAO, and "SAO". "TAO" would be the one to choose.

(Actually "TAO" on DVD+R means just "no RESERVE TRACK". On other media types
it may mean "Track-at-Once" or "Incremental". Those are the write types which
do not need to know the write size in advance.)

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

> Could it be that the file size is too large?

Hardly. libburn inquired the medium capacity before it tried to reserve
the nearly 8000 MiB on the medium. The error message from the drive does not
indicate that it would not accept the size.

> The discs are labelled 8.5Gigabyte

That would be at least 8500000000 bytes and thus should suffice.

> K3b reports a brand new disc as having a capacity of 8.0 GiB and
> Brasero reports 8.5.

That's the difference between International System of Units "GB" and
programmer's "GiB":
8.5 GB = 8500000000/1024/1024/1024 = 7.916241884231567 GiB

I still have a DVD+R DL. (But i don't use them any more because they are
much more error prone than BD-R.) With above "xorriso -toc" run i get
That's a capacity of
4173824*2048 = 8547991552 bytes = 8152 MiB = 7.9609375 GiB.

Have a nice day

Thomas

Thanks for the detailed replies.

Result of

was
I got the same result for the other drive except that the hardware details were different. This was for a total of 4 "used" drives. (I had chucked out one).

The -tao write failed as well, on WRITE (0,16).

I have attached the files.

If it matters: Every failed write, the .iso file was deleted. I had to restore it from another directory. However it survived the -tao write.

Many thanks for the detailed help. I now need to try a xorriso run on the other drive but other duties call.

David

Attached Files

	xorriso.log (15.0 KB, 8 views)
	xorriso_tao.log (16.0 KB, 7 views)

Hi,

> The -tao write failed as well, on WRITE (0,16).
> xorriso_tao.log:
As expected from the failure of RESERVE TRACK, the drive reports again a
problem with its relation to the medium.
It did not give up easily in both cases. The RESERVE TRACK lasted 45 seconds,
the WRITE10 lasted 58 seconds before the error was indicated.

Was the DVD+R DL still reported as blank afterwards ?

Given the fact that several drives dislike these media, we have to regard
the particular media as main suspects.

To my own experience, new drives work a while fine with DVD+R DL, but after
a few months they begin to fail when reading of freshly burned DVD+R DL for
verification. I did not get medium errors reported during the write runs,
though.


> Drive type : vendor 'TSSTcorp' product 'CDDVDW SH-224DB' revision 'SB00'

Not a BD writer, i fear. Else my advise would be to give up on DVD+R DL
and use BD-R.


> If it matters: Every failed write, the .iso file was deleted.
> I had to restore it from another directory. However it survived the -tao
> write.

Uh ? xorriso is not supposed to remove the input image file.
I did not program it that way and nobody ever complained up to now.

I would love to see this riddle solved.
But currently i cannot imagine questions other than:
Did you really check several times that this happens ?
Is it sure that no other program could have deleted the .iso ?
Does it happen if the .iso is in a directory other than /tmp ?


Have a nice day

Thomas

Hello,

No, this is what I got

What triggered this "project" is that I bought a Japanese imported car (Malta drives on the same side as Japan and it seems that the Japanese look after their cars very well and change them at a particularly low mileage). The Radio/GPS needs a disc to boot and the car did not come with one. So in this particular case I need to stay with DL.

Can you burn a Blu-Ray disc as a DVD+R DL?

Re the file deletion, I should have been clearer. K3B and Brasero also deleted the file so the fault prabably lies with another program, called by all these. GenIsoImage?

I gather that you are the author of xorriso. Lovely program. Thanks.

I'll keep playing with this and will keep you posted.

David

Hi,

> I need to stay with DL.

Then get other media from a different brand and hopefully different
manufacturer. xorriso -toc will tell by line "Media product:" (but only
after purchase of the media, i fear).

Try to burn them with your youngest drive.


> [after -tao run]
> Media blocks : 0 readable , 4095872 writable , 4095872 overall

Interesting. The drive now knows the track size which was announced by the
RESERVE TRACK command of the previous experiment.
If this is not the same medium as in the previous experiment, then this
would be another riddle to solve.

Whatever, now the medium is in a state where it might still be possible
to write to the reserved track of ~ 8 GiB. But i know no burn software
which would try to do so. Another write attempt would either fail due
to indigestible status or try to write to the yet unreserved remainder of
the medium.


> Can you burn a Blu-Ray disc as a DVD+R DL?

From the view of a burn program they are quite similar. But you need a Blu-ray
capable drive to read them. I'd expect the car's drive is DVD-only.


> Re the file deletion, I should have been clearer. K3B and Brasero also
> deleted the file so the fault prabably lies with another program, called
> by all these. GenIsoImage?

Do i get it right that you first composed the .iso by help of K3B or Brasero
and that they still ran while you burned the .iso by help of xorriso ?
In this case it would be explainable, as the GUI programs would keep the
images until you abort their burn starter dialog.

Else i would have to theoretisize about unlink-on-close files or similar
oddities ...

The ISO generator is not supposed to remove its output either.
K3B probably used mkisofs or genisoimage, Brasero might have used libisofs.
Xfburn surely uses libisofs.


There stays the question whether an ISO 9660 filesystem is what your car
expects.
From where did you get the instructions for DVD+R DL production ?
Any chance for me to read them in english (or german) ?


> I gather that you are the author of xorriso.

Also the current developer of libburn and libisofs.
Always interested in learning more about the pitfalls of optical recording.


Have a nice day

Thomas

Thanks for this. I can get AOne or Verbatim locally. I don't know AOne but hopefully Varbatim might do the trick. They are certainly pricier - 14.75 vs 9.75 Euros for the Mediarange - which have always worked very well for me. It's too late to go and buy a spindle now as the shops close at 1300 - 1400 on Saturdays but there's always Monday. Thanks again for the help and I'll report on future progress (or the lack threrof)

David

I always liked TDK discs when I was burning optical media. They don't store well, even in a store (uv / window light wrecks them). I tend to keep my blanks in drawers and dark corners.

You might check the .iso image itself. The .iso standard cannot have any "single" file in excess of 4.3GB on it. So if the image is one chapter in excess of 4.3GB aka one .VOB file, that's a fail. Granted there are special extensions and stuff for modern variants, that workaround limits. Depending on how you created the image. Otherwise optical drives are unreliable if you use them. Seemed like 200 successfully burned discs was pushing the limit on drives bitd. But back then computers were effectively space heaters and the optical disc drive located in the hottest corner of said heater. It's been a while since I burned dvd images, but I seem to recall dao, or some sort of -dvd-compat type flags to make it work. Depending on if you're using growisofs, cdparanoia, or cdrdao to do the burn. Perhaps with -overburn as well if you're pushing the size limit.

$ growisofs -speed=4 -dvd-compat -overburn -Z /dev/cdrom=dvd_dl_image.iso

Something like that was how I did burns (never did dual layers though). But when burning multiple copies, having the pre-made .iso was a time saver. Plus everyone got the same image when versions of other things changed. Omitting options if that doesn't work, until it does. For those times when k3b doesn't work, or isn't fast enough. Always verify the disk given the option. Lots of bad media out there. I've had some that were almost transparent, and of course failed.

Hi,

Shadow_7 wrote:
> The .iso standard cannot have any "single" file in excess of 4.3GB on it.

That's not true. Large files are defined as "ISO 9660 Level 3". They get
represented as a group of consecutive files of the same name.
Linux and MS-Windows can handle these files fine. But the BSDs and Solaris
show them in various ill ways. (One still can use xorriso to copy them to
the hard disk as a single file.)


> I seem to recall dao,

That's a write type ("Disc-at-Once") for DVD-R and unformatted DVD-RW.
The other write type for these media is called "Incremental".
DVD+R don't have a distinction of write types. But one has the choice
whether to announce the size of the burn in advance (as is needed for DAO
or CD SAO) or not (as is allowed for Incremental or CD TAO).


> Always verify the disk given the option.

Yes. One has to be aware that most media return more bytes that were
written by the previous burn run and that burn programs often add padding
bytes to the end of the burn to prevent an old bug when Linux reads a
CD burnt by write type TAO.

So one has to curb the number of bytes read from DVD to the number that
were actually written. See:
https://wiki.archlinux.org/index.php...urnt_ISO_image


Have a nice day

Thomas

Just to clarify a couple of points.

1. I created the iso using K3B to copy it off the source disc.
2. The largest file present is 2.97GB.

I've been doing some reading and it seems that I'm one of many people having problems writing DL discs.

Mediarange discs seem to be error prone. Shame really because their CDs and DVDs have never given me any trouble. There seems to be a consensus that Verbatim discs using Azo dyes are the only sane way to go. Hopefully I'll be able to get a spindle tomorrow.

Thanks for the feedback

D

Hi,

if you have a working medium to copy from, then consider to copy a plain
image from the medium without altering or repacking its content.
This will preserve the filesystem type (maybe UDF and not ISO 9660 ?)
and possible boot equipment of the original medium

I am still trying to learn what procedure K3B offers to copy a medium to
an image. But as shell user i would anyways use the classic program dd:
Afterwards one may use the file "$HOME"/dvddl.img like the /tmp/*.iso
file of our previous adventures.

Whatever, the finest image does not help if we can't get it onto medium.


> There seems to be a consensus that Verbatim discs using Azo dyes are
> the only sane way to go.

Verbatim is known for not too bad quality. A special advantage is that they
do not sell media from a wide range of other manufacturers. DVDs are mostly
from their momma company Mitsubishi Kagaku Media. But recently they began to
sell BD-RE from CMC Magnetics.
Whatever, Verbatim gives you best chance to get a medium from a different
manufacturer than other brands.


Have a nice day

Thomas