Re: Linux M-Disc support

--000000000000e3074905e29c830a
Content-Type: text/plain; charset="UTF-8"

Sorry for all the typos. I try to run directly on the system console to
avoid creating a coaster if SSH decides to hang up. As a result, I couldn't
copy-n-paste exactly what happened. I did take pictures on my phone, but
apparently didn't copy to the email very well :-(  But many thanks for your
help.

On Wed, Jun 29, 2022 at 4:44 AM Thomas Schmitt <[email protected]> wrote:

> Hi,
>
> First of all: Congrats to the success and thanks for the report.
>
> I have some comments and corrections for the list archive, though:
>
> Paul von Behren wrote:
> > using xorrisofs, copied the ISO using scp to a Ubuntu system
> > with the SATA burner, where I used xorisso-as cdrecord.--for_backup
>
> --for_backup has to be used with xorrisofs (the -as mkisofs emulation),
> not with xorrecord (the -as cdrecord emulation).
> Its purpose is to put an array of MD5 sums to the end of the ISO 9660
> filesystem and to add an attribute to each data file which points to
> their respective MD5 entry in the array.
>
> Actually xorrecord would refuse on this option:
>   xorriso : FAILURE : -as cdrskin: Unknown option '--for_backup'
> so i assume that you did it right.
>
> If MD5s were recorded then the -for_backup -check_media run should report
> MD5 related messages, like:
>
>   xorriso : UPDATE : Found matching MD5 superblock tag: start=32 size=18
>   ...
>   xorriso : UPDATE : Found matching MD5 tree tag: start=32 size=9022
>   ...
>   xorriso : UPDATE : Found matching MD5 session tag: start=32 size=1969789
>
> and at the end of the run
>
>   MD5 checks   :        lba ,       size , result
>   MD5 tag range:         32 ,    1969789 , + md5_match
>
> (With multi-session media there are such lines for each session.)
>
>
> > I then used xoriso check_media_r ... to verify the md5s - all were
> > good RC=0.
>
> The proposed xorriso commands are -check_media and -check_md5_r.
>
> There is no -check_media_r. xorriso would refuse:
>   xorriso : FAILURE : Not a known command:  '-check_media_r'
>
>
> > I read a paper that studied failures of burns at various speeds. Even if
> the
> > drive vendor said the drive supported 4x (or faster), the study found
> much
> > fewer failures at slower speed (1x).
>
> My own experience is that healthy drives on healthy media can reliably
> write at the maximum speed which they promise. But a BD drive at 10x speed
> is a frightening experience.
>
> I have a Pioneer BDR-S09 which rotates so fast when reading BD-RE that
> newer Verbatim BD-RE physically break by getting cracks at the rim of
> their inner hole. When the crack reaches the dye, the medium becomes
> unreadable.
> he drive does not react on read speed settings. So the only way to slow
> it down is to curb the willingness of xorriso to take data as fast as
> the drive delivers them. Therefore i use this xorriso speed setting
> command when checkreading BD media by the Pioneer BDR-S09:
>   -read_speed soft_force:6xBD
> "soft_force:" is quite new. Only the recent version 1.5.4 supports it.
>
>
> Have a nice day :)
>
> Thomas
>
>

--000000000000e3074905e29c830a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sorry for all the typos. I try to run directly on the syst=
em console to avoid creating a coaster if SSH decides to hang up. As a resu=
lt, I couldn&#39;t copy-n-paste exactly what happened. I did take pictures =
on my phone, but apparently=C2=A0didn&#39;t copy to the email very well :-(=
=C2=A0=C2=A0But many thanks=C2=A0for your help.</div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jun 29, 2022 at 4:44=
 AM Thomas Schmitt &lt;<a href=3D"mailto:[email protected]">[email protected]=
et</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">Hi,<br>
<br>
First of all: Congrats to the success and thanks for the report.<br>
<br>
I have some comments and corrections for the list archive, though:<br>
<br>
Paul von Behren wrote:<br>
&gt; using xorrisofs, copied the ISO using scp to a Ubuntu system<br>
&gt; with the SATA burner, where I used xorisso-as cdrecord.--for_backup<br=
>
<br>
--for_backup has to be used with xorrisofs (the -as mkisofs emulation),<br>
not with xorrecord (the -as cdrecord emulation).<br>
Its purpose is to put an array of MD5 sums to the end of the ISO 9660<br>
filesystem and to add an attribute to each data file which points to<br>
their respective MD5 entry in the array.<br>
<br>
Actually xorrecord would refuse on this option:<br>
=C2=A0 xorriso : FAILURE : -as cdrskin: Unknown option &#39;--for_backup&#3=
9;<br>
so i assume that you did it right.<br>
<br>
If MD5s were recorded then the -for_backup -check_media run should report<b=
r>
MD5 related messages, like:<br>
<br>
=C2=A0 xorriso : UPDATE : Found matching MD5 superblock tag: start=3D32 siz=
e=3D18<br>
=C2=A0 ...<br>
=C2=A0 xorriso : UPDATE : Found matching MD5 tree tag: start=3D32 size=3D90=
22<br>
=C2=A0 ...<br>
=C2=A0 xorriso : UPDATE : Found matching MD5 session tag: start=3D32 size=
=3D1969789<br>
<br>
and at the end of the run<br>
<br>
=C2=A0 MD5 checks=C2=A0 =C2=A0:=C2=A0 =C2=A0 =C2=A0 =C2=A0 lba ,=C2=A0 =C2=
=A0 =C2=A0 =C2=A0size , result<br>
=C2=A0 MD5 tag range:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A032 ,=C2=A0 =C2=A0 19=
69789 , + md5_match<br>
<br>
(With multi-session media there are such lines for each session.)<br>
<br>
<br>
&gt; I then used xoriso check_media_r ... to verify the md5s - all were<br>
&gt; good RC=3D0.<br>
<br>
The proposed xorriso commands are -check_media and -check_md5_r.<br>
<br>
There is no -check_media_r. xorriso would refuse:<br>
=C2=A0 xorriso : FAILURE : Not a known command:=C2=A0 &#39;-check_media_r&#=
39;<br>
<br>
<br>
&gt; I read a paper that studied=C2=A0failures of burns at various speeds. =
Even if the<br>
&gt; drive vendor said the drive supported=C2=A04x (or faster), the study f=
ound much<br>
&gt; fewer failures at slower speed (1x).<br>
<br>
My own experience is that healthy drives on healthy media can reliably<br>
write at the maximum speed which they promise. But a BD drive at 10x speed<=
br>
is a frightening experience.<br>
<br>
I have a Pioneer BDR-S09 which rotates so fast when reading BD-RE that<br>
newer Verbatim BD-RE physically break by getting cracks at the rim of<br>
their inner hole. When the crack reaches the dye, the medium becomes<br>
unreadable.<br>
he drive does not react on read speed settings. So the only way to slow<br>
it down is to curb the willingness of xorriso to take data as fast as<br>
the drive delivers them. Therefore i use this xorriso speed setting<br>
command when checkreading BD media by the Pioneer BDR-S09:<br>
=C2=A0 -read_speed soft_force:6xBD<br>
&quot;soft_force:&quot; is quite new. Only the recent version 1.5.4 support=
s it.<br>
<br>
<br>
Have a nice day :)<br>
<br>
Thomas<br>
<br>
</blockquote></div>

--000000000000e3074905e29c830a--