growisofs 7.1: problem past first layer on BD-R DL

Dennis Vshivkov <[email protected]>
Newsgroups gmane.comp.audio.cd-record
Message-ID <20120910014121.GA26633@ubyak>
Hi all,

having been successfully using growisofs for many years with
varying DVD SL/DL and BD-R SL media, I've been unpleasantly
stung today, trying to write BD-R DL for the first time.

Software versions:

    $ uname -a
    Linux hostname 2.6.39-bpo.2-amd64 #1 SMP Thu Aug 4 11:42:06 UTC 2011 x86_64 GNU/Linux

    $ cat /etc/debian_version 
    6.0.5

    $ growisofs -version
    * growisofs by <[email protected]>, version 7.1,
      front-ending to genisoimage: genisoimage 1.1.11 (Linux)

Command line (used to successfully burn very many a BD-R SL on
the same machine, varying -speed accordingly):

    $ growisofs -use-the-force-luke=spare:none -speed=4 \
	-Z /dev/br <genisoimage-options-here...>

The media is VERBAT/IMf, BD-R DL 1--6x by Mitsubishi Kagaku
Media Co, purchased in Tokyo.  The first failure was at 6x
speed, the second at 4x.  Both times, it ended like so, at the
same LBA=ba7410h offset:

     50.04% done, estimate finish Mon Sep 10 00:43:45 2012
     50.06% done, estimate finish Mon Sep 10 00:43:46 2012
     50.09% done, estimate finish Mon Sep 10 00:43:45 2012
    :-[ WRITE@LBA=ba7410h failed with SK=5h/INVALID ADDRESS FOR WRITE]: Invalid argument
    :-( write failed: Invalid argument
    /dev/br: flushing cache
    /dev/br: closing track
    /dev/br: closing session
    /dev/br: reloading tray

Here's the media info _after_ the failure (also shows the
hardware and firmware being used):

    $ dvd+rw-mediainfo /dev/br 
    INQUIRY:                [PIONEER ][BD-RW   BDR-206D][1.56]
    GET [CURRENT] CONFIGURATION:
     Mounted Media:         41h, BD-R SRM
     Media ID:              VERBAT/IMf
     Current Write Speed:   8.0x4495=35960KB/s
     Write Speed #0:        12.0x4495=53940KB/s
     Write Speed #1:        8.0x4495=35960KB/s
     Write Speed #2:        6.0x4495=26970KB/s
     Write Speed #3:        4.0x4495=17980KB/s
     Write Speed #4:        2.0x4495=8990KB/s
     Speed Descriptor#0:    00/24438783 [email protected]=35960KB/s [email protected]=35960KB/s
     Speed Descriptor#1:    00/24438783 [email protected]=26970KB/s [email protected]=26970KB/s
     Speed Descriptor#2:    00/24438783 [email protected]=17980KB/s [email protected]=17980KB/s
     Speed Descriptor#3:    00/24438783 [email protected]=8990KB/s [email protected]=8990KB/s
    READ DISC INFORMATION:
     Disc status:           appendable
     Number of Sessions:    2
     State of Last Session: incomplete
     "Next" Track:          2
     Number of Tracks:      2
    READ TRACK INFORMATION[#1]:
     Track State:           partial incremental
     Track Start Address:   0*2KB
     Free Blocks:           0*2KB
     Track Size:            12219424*2KB
     Last Recorded Address: 12219407*2KB
    READ TRACK INFORMATION[#2]:
     Track State:           incomplete incremental
     Track Start Address:   12219424*2KB
     Next Writable Address: 12219456*2KB
     Free Blocks:           12219328*2KB
     Track Size:            12219360*2KB
     Last Recorded Address: 12219439*2KB
    FABRICATED TOC:
     Track#1  :             14@0
     Track#AA :             14@12219408
     Multi-session Info:    #1@0
    READ CAPACITY:          12219408*2048=25025347584

The error happens after exactly half the capacity plus one
single 32 KiB block.  The stop point, in 2 KiB block terms:

    0xba7410 == 12219408 == 24438784 / 2 + 16

After the failure, the recorded 12219408 blocks of 2 KiB read
back in completely fine.  The final blocks of the session
contain garbage.  It's also possible to then write more sessions
to the remainder of the disk (via -use-the-force-luke=seek:xyz)
successfully.

It seems there may be a problem when just starting to write the
second layer.

Before I continue to experiment with the costly BD-R DL blanks
(I haven't any BD-RE DL, so the next thing is to try cdrskin, I
suppose, or removing -use-the-force-luke=spare:none), can anyone
please share similar or contrary experience with the same or
similar software, hardware and/or media?  Any clues to the
reason or any other hints?

(Please refrain from suggesting to check various cabling, hard
disk speed issues, automount interference and other non-specific
things.  A few BD-R SL, including VERBAT/IMe from the same
series by MKM, were recorded before and after these problems on
the same rig, zero issues.)

Cheers,

-- 
/Dennis Vshivkov <[email protected]>


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/20120910014121.GA26633@ubyak
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.