Re: Linux M-Disc support

--00000000000067189505e283f01d
Content-Type: text/plain; charset="UTF-8"

-I bought a Samsung USB drive when m-disks were new and got some media to
backup my Windows laptop. I was using Acronis and the boot and restore from
USB was a pain; so I have left over unused disks I should use. The disks I
did create are still readable on Linux. FWIW, here's output from xorriso
-to from two mdisks. One is a Verbatim and the other is Millentia; one was
written. These reports are from an LG SATA BD drive.

Drive current: -dev '/dev/sr0'
Drive access : exclusive:unrestricted
Drive type   : vendor 'HL-DT-ST' product 'BD-RE WH16NS40' revision '1.02'
Drive id     : 'K9AE5EA4251 '
Media current: BD-R sequential recording
Media product: MILLEN/MR1/0 , Millenniata Inc.
Media status : is blank
Media blocks : 0 readable , 12219392 writable , 12219392 overall
Media summary: 0 sessions, 0 data blocks, 0 data, 23.3g free

Drive current: -dev '/dev/sr0'
Drive access : exclusive:unrestricted
Drive type   : vendor 'HL-DT-ST' product 'BD-RE WH16NS40' revision '1.02'
Drive id     : 'K9AE5EA4251 '
Media current: BD-R sequential recording, Pseudo Overwrite formatted
Media product: VERBAT/IMk/0 , Mitsubishi Kagaku Media Co.
Media status : is unsuitable , is POW formatted
Media blocks : 35185280 readable , 12906880 unused , 48092160 overall
Media summary: unsuitable Pseudo Overwrite formatted BD-R

I will try to burn an m-disk next with xorriso and let you know how it
goes.

Paul

On Tue, Jun 28, 2022 at 6:50 AM Thomas Schmitt <[email protected]> wrote:

> Hi,
>
> Paul von Behren wrote:
> > Can xorriso burn/engrave an M-Disc? Can any other Linux SW?
>
> Yes to both, although rarely tested.
> In my mailbox i find libburn user reports only for BD-R M-Discs.
>
> M-Disc is entirely a matter of drive and medium. The burn programs get
> the media info from the drive which presents M-Disc as DVD+R or BD-R.
> (Verbatim seems to sell M-Disc DVD as "DVD R" omitting the significant
> difference between DVD-R and DVD+R. But i remember that DVD+R was
> mentioned when the M-Disc technology was announced.)
>
> So if you really want to pay the price difference between M-Disc and
> other write-once media, then give it a try with your favorite burn
> program for DVD or BD.
> I would of course be glad if you choose xorriso or cdrskin.
>
> Please report the outcome.
> As said: Reports are rare.
>
> ----------------------------------------------------------------------
>
> If the burn run looks successful, consider to run
>
>   xorriso -for_backup -indev /dev/sr0 -check_media --
>
> to get an impression of readability.
>
> If you use xorriso to create an ISO 9660 filesystem, then consider to
> use -for_backup to equip the data files and the overall filesystem with
> MD5 checksums. (With xorriso's mkisofs emulation the option begins by
> two dashes: --for_backup.)
>
> A xorriso run with -for_backup ... -check_media will then verify the
> overall checksums.
> But even without recorded MD5s it will check the readability of all data
> blocks of the written area.
>
>
> If you recorded MD5 and want to check the single file checksums:
>
>   xorriso -for_backup -indev /dev/sr0 -check_md5_r sorry / --
>
> This will report on stdout each file which fails to match its recorded
> MD5. Informational messages and pacifiers appear on stderr.
> The exit status of xorriso will indicate whether all was fine (0) or
> whether files failed the test (not 0, actually 32).
> This check works only if indeed MD5s were recorded by xorriso.
>
> Consider to repeat this checking regularly to get an impression how your
> recorded files are doing.
>
>
> Have a nice day :)
>
> Thomas
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr">-I bought a Samsung USB drive when m-disk=
s were new and got some media to backup my Windows laptop. I was using Acro=
nis and the boot and restore from USB was a pain; so I have left over unuse=
d disks I should use. The disks I did create=C2=A0are still readable on Lin=
ux. FWIW, here&#39;s output=C2=A0from xorriso -to from two mdisks. One is a=
 Verbatim and the other is Millentia; one was written. These reports are fr=
om an LG SATA BD drive.<div><br></div><div>Drive current: -dev &#39;/dev/sr=
0&#39;<br>Drive access : exclusive:unrestricted<br>Drive type =C2=A0 : vend=
or &#39;HL-DT-ST&#39; product &#39;BD-RE WH16NS40&#39; revision &#39;1.02&#=
39;<br>Drive id =C2=A0 =C2=A0 : &#39;K9AE5EA4251 &#39;<br>Media current: BD=
-R sequential recording<br>Media product: MILLEN/MR1/0 , Millenniata Inc.<b=
r>Media status : is blank<br>Media blocks : 0 readable , 12219392 writable =
, 12219392 overall<br>Media summary: 0 sessions, 0 data blocks, 0 data, 23.=
3g free</div><div><br>Drive current: -dev &#39;/dev/sr0&#39;<br>Drive acces=
s : exclusive:unrestricted<br>Drive type =C2=A0 : vendor &#39;HL-DT-ST&#39;=
 product &#39;BD-RE WH16NS40&#39; revision &#39;1.02&#39;<br>Drive id =C2=
=A0 =C2=A0 : &#39;K9AE5EA4251 &#39;<br>Media current: BD-R sequential recor=
ding, Pseudo Overwrite formatted<br>Media product: VERBAT/IMk/0 , Mitsubish=
i Kagaku Media Co.<br>Media status : is unsuitable , is POW formatted<br>Me=
dia blocks : 35185280 readable , 12906880 unused , 48092160 overall<br>Medi=
a summary: unsuitable Pseudo Overwrite formatted BD-R</div><div><br></div><=
div>I will try to burn an m-disk next with xorriso and let you know how it =
goes.=C2=A0</div><div><br></div><div>Paul<br><div><br></div></div></div><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jun 2=
8, 2022 at 6:50 AM Thomas Schmitt &lt;<a href=3D"mailto:[email protected]" =
target=3D"_blank">[email protected]</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
Paul von Behren wrote:<br>
&gt; Can xorriso burn/engrave an M-Disc? Can any other Linux SW?<br>
<br>
Yes to both, although rarely tested.<br>
In my mailbox i find libburn user reports only for BD-R M-Discs.<br>
<br>
M-Disc is entirely a matter of drive and medium. The burn programs get<br>
the media info from the drive which presents M-Disc as DVD+R or BD-R.<br>
(Verbatim seems to sell M-Disc DVD as &quot;DVD R&quot; omitting the signif=
icant<br>
difference between DVD-R and DVD+R. But i remember that DVD+R was<br>
mentioned when the M-Disc technology was announced.)<br>
<br>
So if you really want to pay the price difference between M-Disc and<br>
other write-once media, then give it a try with your favorite burn<br>
program for DVD or BD.<br>
I would of course be glad if you choose xorriso or cdrskin.<br>
<br>
Please report the outcome.<br>
As said: Reports are rare.<br>
<br>
----------------------------------------------------------------------<br>
<br>
If the burn run looks successful, consider to run<br>
<br>
=C2=A0 xorriso -for_backup -indev /dev/sr0 -check_media --<br>
<br>
to get an impression of readability.<br>
<br>
If you use xorriso to create an ISO 9660 filesystem, then consider to<br>
use -for_backup to equip the data files and the overall filesystem with<br>
MD5 checksums. (With xorriso&#39;s mkisofs emulation the option begins by<b=
r>
two dashes: --for_backup.)<br>
<br>
A xorriso run with -for_backup ... -check_media will then verify the<br>
overall checksums.<br>
But even without recorded MD5s it will check the readability of all data<br=
>
blocks of the written area.<br>
<br>
<br>
If you recorded MD5 and want to check the single file checksums:<br>
<br>
=C2=A0 xorriso -for_backup -indev /dev/sr0 -check_md5_r sorry / --<br>
<br>
This will report on stdout each file which fails to match its recorded<br>
MD5. Informational messages and pacifiers appear on stderr.<br>
The exit status of xorriso will indicate whether all was fine (0) or<br>
whether files failed the test (not 0, actually 32).<br>
This check works only if indeed MD5s were recorded by xorriso.<br>
<br>
Consider to repeat this checking regularly to get an impression how your<br=
>
recorded files are doing.<br>
<br>
<br>
Have a nice day :)<br>
<br>
Thomas<br>
<br>
</blockquote></div>
</div>

--00000000000067189505e283f01d--