Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Nov 2022 20:32:52 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Cc:        =?UTF-8?Q?Chlast=C3=A1k_Miroslav?= <mira@chlastak.cz>,  FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   Re: loader.conf and rootdev option for memory disk
Message-ID:  <CANCZdfpNtRnqoirja30q_7gotE=Z9w2MG-XhjFETwNQU=XzgLQ@mail.gmail.com>
In-Reply-To: <20221120100046.b44741ca341c1593a72f594b@dec.sakura.ne.jp>
References:  <2E58D34B-F8C5-4291-B019-9E24F56DC3DF@chlastak.cz> <CANCZdfqGhHXCJtUOctpoB-sAuxSdzJZERSBritTazp_uragZ=Q@mail.gmail.com> <F3702494-1433-4324-B972-52FBD84EFFD8@chlastak.cz> <20221120055845.366367f1d371ae4d6eb8d747@dec.sakura.ne.jp> <97A75B5E-6C38-4CFB-9978-7E254595D980@chlastak.cz> <20221120100046.b44741ca341c1593a72f594b@dec.sakura.ne.jp>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
On Sat, Nov 19, 2022 at 6:01 PM Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
wrote:

> But your previous post shows rootdev= there didn't work, and needed
> setting vfs.root.mountfrom=.
>
> OTOH, rootdev= is reported to work in efi/boot/freebsd/loader.env (with
> efi loader) on freebsd-users-jp ML (as it's Japanese ML, in Japanese)
> this year.
>
> So /boot/defaults/loader.conf (/usr/src/stand/defaults/loader.conf)
> should be fixed, and what should be set in loader.env should be
> documented.
>
>  *Dedicated brand-new manpage or in boot.8 (or in loader.8 describing
>   rootdev, or loader.conf.8 in contrast with itself).
>

Reading the code it's complicated.

rootdev looks like it overrides the default root... unless
vfs.root.mountfrom
has already been set.


>
> On Sat, 19 Nov 2022 22:31:42 +0100
> Chlasták Miroslav <mira@chlastak.cz> wrote:
>
> > Look at the file /boot/defaults/loader.conf:
> >
> > …
> > ###  Initial memory disk settings  ###########################
> > #mdroot_load="YES"              # The "mdroot" prefix is arbitrary.
> > #mdroot_type="md_image"         # Create md(4) disk at boot.
> > #mdroot_name="/boot/root.img"   # Path to a file containing the image.
> > #rootdev="ufs:/dev/md0"         # Set the root filesystem to md(4)
> device.
> > …
> >
> > —
> > Mira
> >
> > > On 19 Nov 2022, at 21:58, Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
> wrote:
> > >
> > > IIUC, rootdev should be set in loader.env, if needed.
> > > `man 5 loader.conf` has nothing about rootdev variable.
> > >
> > > (It's undocumented, IIRC.)
> > >
> > >
> > > On Sat, 19 Nov 2022 19:57:47 +0100
> > > Chlasták Miroslav <mira@chlastak.cz <mailto:mira@chlastak.cz>> wrote:
> > >
> > >> I have my device working for now - but the question is - Is the
> documentation and example for “rootdev” right or not?
> > >>
> > >> —
> > >> Mira
> > >>
> > >>> On 18 Nov 2022, at 21:13, Warner Losh <imp@bsdimp.com <mailto:
> imp@bsdimp.com>> wrote:
> > >>>
> > >>>
> > >>>
> > >>> On Fri, Nov 18, 2022 at 12:57 PM Chlasták Miroslav <mira@chlastak.cz
> <mailto:mira@chlastak.cz> <mailto:mira@chlastak.cz <mailto:
> mira@chlastak.cz>>> wrote:
> > >>> Hi all,
> > >>>
> > >>> In the /boot/defaults/loader.conf are these options for memory disk
> settings:
> > >>>
> > >>> #mdroot_load="YES"              # The "mdroot" prefix is arbitrary.
> > >>> #mdroot_type="md_image"         # Create md(4) disk at boot.
> > >>> #mdroot_name="/boot/root.img"   # Path to a file containing the
> image.
> > >>> #rootdev="ufs:/dev/md0"         # Set the root filesystem to md(4)
> device.
> > >>>
> > >>>
> > >>> But - is this example for rootdev option still right? Because
> “ufs:/dev/md0” works fine on freebsd 12.1, but on freebsd 12.3 this does
> not work and generates error message:
> > >>>
> > >>> Can’t determine root device
> > >>>
> > >>>
> > >>> When I use this option with value “/dev/md0” or “md0” (even with
> this option commented out), so the machine boots correctly without any
> error.
> > >>>
> > >>> I think you want vfs.root.mountfrom= instead of rootdev= here.
> > >>>
> > >>> Warner
> > >>>
> > >>> —
> > >>> Mira
> > >>
> > >
> > >
> > > --
> > > 青木 知明  [Tomoaki AOKI]    <junchoon@dec.sakura.ne.jp <mailto:
> junchoon@dec.sakura.ne.jp>>
> >
>
>
> --
> 青木 知明  [Tomoaki AOKI]    <junchoon@dec.sakura.ne.jp>
>
>

[-- Attachment #2 --]
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Nov 19, 2022 at 6:01 PM Tomoaki AOKI &lt;<a href="mailto:junchoon@dec.sakura.ne.jp">junchoon@dec.sakura.ne.jp</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">But your previous post shows rootdev= there didn&#39;t work, and needed<br>
setting vfs.root.mountfrom=.<br>
<br>
OTOH, rootdev= is reported to work in efi/boot/freebsd/loader.env (with<br>
efi loader) on freebsd-users-jp ML (as it&#39;s Japanese ML, in Japanese)<br>
this year.<br>
<br>
So /boot/defaults/loader.conf (/usr/src/stand/defaults/loader.conf)<br>
should be fixed, and what should be set in loader.env should be<br>
documented.<br>
<br>
 *Dedicated brand-new manpage or in boot.8 (or in loader.8 describing<br>
  rootdev, or loader.conf.8 in contrast with itself).<br></blockquote><div><br></div><div>Reading the code it&#39;s complicated.</div><div><br></div><div>rootdev looks like it overrides the default root... unless vfs.root.mountfrom</div><div>has already been set.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
On Sat, 19 Nov 2022 22:31:42 +0100<br>
Chlasták Miroslav &lt;<a href="mailto:mira@chlastak.cz" target="_blank">mira@chlastak.cz</a>&gt; wrote:<br>
<br>
&gt; Look at the file /boot/defaults/loader.conf:<br>
&gt; <br>
&gt; …<br>
&gt; ###  Initial memory disk settings  ###########################<br>
&gt; #mdroot_load=&quot;YES&quot;              # The &quot;mdroot&quot; prefix is arbitrary.<br>
&gt; #mdroot_type=&quot;md_image&quot;         # Create md(4) disk at boot.<br>
&gt; #mdroot_name=&quot;/boot/root.img&quot;   # Path to a file containing the image.<br>
&gt; #rootdev=&quot;ufs:/dev/md0&quot;         # Set the root filesystem to md(4) device.<br>
&gt; …<br>
&gt; <br>
&gt; —<br>
&gt; Mira<br>
&gt; <br>
&gt; &gt; On 19 Nov 2022, at 21:58, Tomoaki AOKI &lt;<a href="mailto:junchoon@dec.sakura.ne.jp" target="_blank">junchoon@dec.sakura.ne.jp</a>&gt; wrote:<br>
&gt; &gt; <br>
&gt; &gt; IIUC, rootdev should be set in loader.env, if needed.<br>
&gt; &gt; `man 5 loader.conf` has nothing about rootdev variable.<br>
&gt; &gt; <br>
&gt; &gt; (It&#39;s undocumented, IIRC.)<br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; On Sat, 19 Nov 2022 19:57:47 +0100<br>
&gt; &gt; Chlasták Miroslav &lt;<a href="mailto:mira@chlastak.cz" target="_blank">mira@chlastak.cz</a> &lt;mailto:<a href="mailto:mira@chlastak.cz" target="_blank">mira@chlastak.cz</a>&gt;&gt; wrote:<br>
&gt; &gt; <br>
&gt; &gt;&gt; I have my device working for now - but the question is - Is the documentation and example for “rootdev” right or not?<br>
&gt; &gt;&gt; <br>
&gt; &gt;&gt; —<br>
&gt; &gt;&gt; Mira<br>
&gt; &gt;&gt; <br>
&gt; &gt;&gt;&gt; On 18 Nov 2022, at 21:13, Warner Losh &lt;<a href="mailto:imp@bsdimp.com" target="_blank">imp@bsdimp.com</a> &lt;mailto:<a href="mailto:imp@bsdimp.com" target="_blank">imp@bsdimp.com</a>&gt;&gt; wrote:<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; On Fri, Nov 18, 2022 at 12:57 PM Chlasták Miroslav &lt;<a href="mailto:mira@chlastak.cz" target="_blank">mira@chlastak.cz</a> &lt;mailto:<a href="mailto:mira@chlastak.cz" target="_blank">mira@chlastak.cz</a>&gt; &lt;mailto:<a href="mailto:mira@chlastak.cz" target="_blank">mira@chlastak.cz</a> &lt;mailto:<a href="mailto:mira@chlastak.cz" target="_blank">mira@chlastak.cz</a>&gt;&gt;&gt; wrote:<br>
&gt; &gt;&gt;&gt; Hi all,<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; In the /boot/defaults/loader.conf are these options for memory disk settings:<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; #mdroot_load=&quot;YES&quot;              # The &quot;mdroot&quot; prefix is arbitrary.<br>
&gt; &gt;&gt;&gt; #mdroot_type=&quot;md_image&quot;         # Create md(4) disk at boot.<br>
&gt; &gt;&gt;&gt; #mdroot_name=&quot;/boot/root.img&quot;   # Path to a file containing the image.<br>
&gt; &gt;&gt;&gt; #rootdev=&quot;ufs:/dev/md0&quot;         # Set the root filesystem to md(4) device.<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; But - is this example for rootdev option still right? Because “ufs:/dev/md0” works fine on freebsd 12.1, but on freebsd 12.3 this does not work and generates error message:<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; Can’t determine root device<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; When I use this option with value “/dev/md0” or “md0” (even with this option commented out), so the machine boots correctly without any error.<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; I think you want vfs.root.mountfrom= instead of rootdev= here.<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; Warner<br>
&gt; &gt;&gt;&gt; <br>
&gt; &gt;&gt;&gt; —<br>
&gt; &gt;&gt;&gt; Mira<br>
&gt; &gt;&gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; -- <br>
&gt; &gt; 青木 知明  [Tomoaki AOKI]    &lt;<a href="mailto:junchoon@dec.sakura.ne.jp" target="_blank">junchoon@dec.sakura.ne.jp</a> &lt;mailto:<a href="mailto:junchoon@dec.sakura.ne.jp" target="_blank">junchoon@dec.sakura.ne.jp</a>&gt;&gt;<br>
&gt; <br>
<br>
<br>
-- <br>
青木 知明  [Tomoaki AOKI]    &lt;<a href="mailto:junchoon@dec.sakura.ne.jp" target="_blank">junchoon@dec.sakura.ne.jp</a>&gt;<br>
<br>
</blockquote></div></div>
help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpNtRnqoirja30q_7gotE=Z9w2MG-XhjFETwNQU=XzgLQ>