From nobody Fri Nov 18 20:13:31 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NDSfJ1Sp4z4h9HH for ; Fri, 18 Nov 2022 20:13:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NDSfJ1255z3knF for ; Fri, 18 Nov 2022 20:13:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x631.google.com with SMTP id gv23so15714614ejb.3 for ; Fri, 18 Nov 2022 12:13:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=PgqSeQ27DIGzOG3ulltysje36PLCgTpDdODFBvx121I=; b=1ssUpZWg++wYHcBJesi0g0HheYhd/tZnxPAbYAMvKjMTZtrQW5kahNq9YRRDtS/vuY jO/1ZKFpiR0kfSvWWokvMD3mUnBnFmo+Tx0q9ttm0rFxSYGqSQTXnUTWVKwEiF4VCKc4 36hEb/cy5H8KF7uOOfJs4a71tpRhwOkAyxZwq2rwC3/e5GS3vUGyMFNfkIdh8Z8gfhMX tkVklyIks/Thg6CU1kip8Dw2o3lbkbsB1qrVJjxWBIePyQCtB0whT5yiXG1RlpI6TJMz 3OdiVl5YhbqtN/Vr9b0PxPYRVPMbeFX369/Cz0qY8s/rtOZDVTYFbXXebH4h00e0j9Om 0txg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=PgqSeQ27DIGzOG3ulltysje36PLCgTpDdODFBvx121I=; b=z59QeNkSD9aDbmeKjMsotBNLi2UpKv44RpSL5qLtWG4h/j063A1MQx9c5vz49zGhMZ 9FBF3KzIeEbu8yYtEfq9jlzvy9HDpN1AOo+8txTvf/RxexydvtCaBU2IsEi8sYUMZKdj yb6UEdlQPNsfelCn+vgG1bBBrzHtxjXbrxreveP+3xa2g9/f2XrYyaTAoBWPQkTs8/F3 QJqlZh2Odt11FII6EiFksQculBA8tPaiNqjuv9wE7U+Ho6nePIGU8FQEs4p5AqzbvHRe X4h8jRAuzs4dawgt9o42l2UEYi6U+IAGBUwGrZY9ZfqAy31o0bDtbC0X5f7uO7WBdoPq xyhQ== X-Gm-Message-State: ANoB5pmdtf1zUIeN8UGavfBnQ5CrkfydAi9rhbmxVWrJ/C7qFa91JaG7 FnqBU8ErPKif+oobboKoTQkj8sEct8GuYZoChPmUEfQKzAvh6g== X-Google-Smtp-Source: AA0mqf7GlilwpQDpZTE38DIUuzSdGVuQMPfBzJPn0JU9gyQlqHPoSmCwv2P/E/vmaRh+E5bUTTZA+qr1m3Bn29dW8DA= X-Received: by 2002:a17:906:b210:b0:7ae:d116:fabb with SMTP id p16-20020a170906b21000b007aed116fabbmr7204346ejz.317.1668802422682; Fri, 18 Nov 2022 12:13:42 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <2E58D34B-F8C5-4291-B019-9E24F56DC3DF@chlastak.cz> In-Reply-To: <2E58D34B-F8C5-4291-B019-9E24F56DC3DF@chlastak.cz> From: Warner Losh Date: Fri, 18 Nov 2022 13:13:31 -0700 Message-ID: Subject: Re: loader.conf and rootdev option for memory disk To: =?UTF-8?Q?Chlast=C3=A1k_Miroslav?= Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="0000000000009ae2aa05edc4577c" X-Rspamd-Queue-Id: 4NDSfJ1255z3knF X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000009ae2aa05edc4577c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Nov 18, 2022 at 12:57 PM Chlast=C3=A1k Miroslav = wrote: > Hi all, > > In the /boot/defaults/loader.conf are these options for memory disk > settings: > > #mdroot_load=3D"YES" # The "mdroot" prefix is arbitrary. > #mdroot_type=3D"md_image" # Create md(4) disk at boot. > #mdroot_name=3D"/boot/root.img" # Path to a file containing the image. > #rootdev=3D"ufs:/dev/md0" # Set the root filesystem to md(4) devi= ce. > > > But - is this example for rootdev option still right? Because > =E2=80=9Cufs:/dev/md0=E2=80=9D works fine on freebsd 12.1, but on freebsd= 12.3 this does > not work and generates error message: > > Can=E2=80=99t determine root device > > > When I use this option with value =E2=80=9C/dev/md0=E2=80=9D or =E2=80=9C= md0=E2=80=9D (even with this > option commented out), so the machine boots correctly without any error. > I think you want vfs.root.mountfrom=3D instead of rootdev=3D here. Warner > =E2=80=94 > Mira > --0000000000009ae2aa05edc4577c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Nov 18, 2022 at 12:57 PM Chla= st=C3=A1k Miroslav <mira@chlastak.cz= > wrote:
=
Hi all,

In the= /boot/defaults/loader.conf are these options for memory disk settings:

#mdroot_load=3D"YES= "=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 # The "mdroot&q= uot; prefix is arbitrary.
#mdroot_type=3D= "md_image" =C2=A0 =C2=A0 =C2=A0 =C2=A0 # Create md(4) disk at boo= t.
#mdroot_name=3D"/boot/root.img&qu= ot; =C2=A0 # Path to a file containing the image.
#rootdev=3D"ufs:/dev/md0" =C2=A0 =C2=A0 =C2=A0 =C2=A0 # = Set the root filesystem to md(4) device.


But - is this example for rootdev option still right? Because =E2= =80=9Cufs:/dev/md0=E2=80=9D works fine on freebsd 12.1, but on freebsd 12.3= this does not work and generates error message:

Can=E2=80=99t determine root= device


When I use this option with va= lue =E2=80=9C/dev/md0=E2=80=9D or =E2=80=9Cmd0=E2=80=9D (even with this opt= ion commented out),=C2=A0so the machine boots correctly without any error.<= /div>

I think you want=C2=A0vfs.root.= mountfrom=3D instead of rootdev=3D here.

Warner
=C2=A0
=E2=80=94=
Mira
--0000000000009ae2aa05edc4577c--