Re: resuming writing an unclosed DVD+R track

[Thomas Schmitt]

Hi,

Ivan Shmakov wrote:
>   484114432/4700372992 (10.3%) @5.4x, remaining 11:01 RBU 100.0% UBU  98.4%
> :-[ WRITE@LBA=39b60h failed with SK=4h/LOGICAL UNIT COMMUNICATION TIMEOUT]:
> Input/output error

SK=4 means "Drive error". The ASC/ASQ combination is probably 08/01 and
the message probably stems from the drive's firmware. (Of course the kernel
is free to insert its own Sense Data into the communication between program
and drive.)

Obviously some entity in the chain lost patience with its communications
partner.

Normally i would advise to repeat the burn with a fresh medium.


>  State of Last Session: incomplete
> READ TRACK INFORMATION[#1]:
>  Track State:           invisible
>  Track Start Address:   0*2KB
>  Next Writable Address: 236400*2KB

According to MMC specs, DVD+R can have multiple tracks open. It's not so
clear from the text wether this persists over ejecting and loading the
medium.

Whatever, this does not fit well into the media model of libburn, which
stems from the properties of CD-R media.
So the only offer which xorriso could make is -close_damaged, which
would possibly close the track somewhere after block 236400. Depending
on the mood of the drive the DVD+R might stay appendable and you could
add more data as second session.


> growisofs -dvd-compat -speed=6
> -use-the-force-luke=seek=236400 -Z /dev/sr0=/dev/loopXX

Interesting to know that Luke Skywalker can override the Next Writable
Address. libburn is willing to do such autocratic things only on
overwritable media (DVD+RW, BD-RE, ...). Normally it opnes a new session
and asks the drive for telling its start address.

> growisofs -dvd-compat -speed=6 -overburn
> -use-the-force-luke=seek=2288256 -Z /dev/sr0=/tmp/pieces.Vm3nMUcT

I don't think that -use-the-force-luke=seek= is necessary with this
run, which goes to track/session 2.

> :-[ CLOSE TRACK failed with SK=5h/INVALID FIELD IN CDB]: Input/output error

growisofs seems slightly disoriented here. :-)
But the drive just rejected the unwanted SCSI command and took no offense.


> Finally, I’ve used dmsetup(1) to create a block device that
> maps the copy of the data from the tail of the medium over
> the miswritten portion
> bash# dmsetup create -- sr0.fixed \
>          <(printf %s\\n "0 944640 linear /dev/sr0 0" \
>                "944640 1536 linear /dev/sr0 9153024" \
>                "946176 8198656 linear /dev/sr0 946176")


Now this is a stunt which i shall memorize.
I guess it would work with a second session on the DVD+R as well.


Have a nice day :)

Thomas