From nobody Sun Sep 8 03:34:27 2024 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 4X1bDw28gnz5VR4K for ; Sun, 08 Sep 2024 03:34:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X1bDw1dF3z3wkj for ; Sun, 8 Sep 2024 03:34:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1035.google.com with SMTP id 98e67ed59e1d1-2d8a7c50607so2205731a91.1 for ; Sat, 07 Sep 2024 20:34:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1725766479; x=1726371279; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=w045L12qS3LF9MrLbQvL5Eow/sAdFCKHj2YpHaKLwIg=; b=CZPHDOvcNaqH6v7CBUEyFfa2in2U/LwJGTVPyt+mgqWqbdhmaFVyOZ+Zot5vGQFt+c S+ZoajoiyXvdUb6734AfRX61aRYHw8/Oc1YyXFiE+l08Rfm5rotLfpPQ+3OGzRyBVP7G 5uQprmSmu4PCwBh1EMOSvi+RYcVQHzqqsUfpPpNjYLryhKxW2we7zUqjUyal6z/m4uSB SzGdlG/h2x5BZk2mwmKDRAQuxTKn2s78OJ8eDK+g0jPO3rNbbbg1M2J+da7KWlm7QAmC ZekrTmXzZtPv1l4lRivPg0XGYtd0EM0xGJTcr6qtcEub/CJZPUAubwr9fWv8Dxh7dMUO CJgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725766479; x=1726371279; 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=w045L12qS3LF9MrLbQvL5Eow/sAdFCKHj2YpHaKLwIg=; b=k1SZZsHpy51kllytuCy1eU4hPZaBKfDgnulIBIlSOrGVHFVycMeKTPN2YY2f80iLEM Mze0VuyNlOPoZH6k23esE7GOuZxpYJ8FnkvEN3wyIyXP51SSAqi8LmRs3wBwFA/E18uP hg/um7D3hOtDde1tNbNOYqw+f9pCdHMeME87tQFdoo0Q5VrPv6Ye93Xx7uJzdJZlnUi/ JAnvvOG360R3fvFyUppwrQsDBp5npP9Cg0LVFEGnhwEQFI7XmGnhYlysr9tmFzFSKqfy soOl27aI11Y7z5oESKu2oFmvdCInKgO7YbaNdS/3RbxPI9KO+TPOnWjs7AX8zyatRXt7 zdqg== X-Forwarded-Encrypted: i=1; AJvYcCX4iZEBvWzy/YwKHPgcue5agF9FMzN+hUbdwTLFJ3iVklGCotylHjXANYAZ0s6XDWt75NUSet/WRJNrCRZP3jQ=@freebsd.org X-Gm-Message-State: AOJu0YwzUeF/vJMektVGjYwypeLEZtYxrBUa5pdyTCasa5kVri80JKM5 Yvs37MdcGOv0jkH/+8nRhz41Nz9/xo+JjwXC8mOg17HVfVkXuFcEx0FSAWzyzx6J2lPqhmbEKwZ L/3CXCooFdwduf1lZ9fh8axCEjPcQyMoCajo7YZ1aUFp4nnsF X-Google-Smtp-Source: AGHT+IFcyuCsoxNHrhhZUhe8l1dWYFBeBChsOZFaF7xhkLZeiv02A/A0KSxCuyuV/NfLmP6CoqAgiPxD/3ZlLw44dEQ= X-Received: by 2002:a17:90b:38cc:b0:2d1:ca16:5555 with SMTP id 98e67ed59e1d1-2dad50f9e56mr9276268a91.37.1725766478864; Sat, 07 Sep 2024 20:34:38 -0700 (PDT) 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: <20240908122425.720c256cbe4a0c6ae77ded0d@dec.sakura.ne.jp> In-Reply-To: <20240908122425.720c256cbe4a0c6ae77ded0d@dec.sakura.ne.jp> From: Warner Losh Date: Sat, 7 Sep 2024 21:34:27 -0600 Message-ID: Subject: Re: Loader needs to be updated message To: Tomoaki AOKI Cc: Mark Millard , Current FreeBSD Content-Type: multipart/alternative; boundary="000000000000f03f2d0621935107" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4X1bDw1dF3z3wkj --000000000000f03f2d0621935107 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Sep 7, 2024, 9:24=E2=80=AFPM Tomoaki AOKI wrote: > On Sat, 7 Sep 2024 19:52:53 -0700 > Mark Millard wrote: > > > Tomoaki AOKI wrote on > > Date: Sun, 08 Sep 2024 01:54:28 UTC : > > > > > On Sun, 8 Sep 2024 02:01:02 +0100 > > > void wrote: > > > > > > > On Sun, Sep 08, 2024 at 09:23:02AM +0900, Tomoaki AOKI wrote: > > > > > > > > . . . > > > > > > If not automounted, you can mount ESP manually as msdosfs there, at > > > least for bare-metal host. IIUC, recent installation by bsdinstall > > > creates fstab entry for it by default. > > > > void previously reported: > > > > QUOTE > > # gpart list | grep -E '(Name|type|efi|media)' > > 1. Name: vtbd0p1 > > efimedia: HD(1,GPT,b7731537-61da-11ed-9652-00a0981073a7,0x28,0x400) > > rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f > > type: freebsd-boot > > 2. Name: vtbd0p2 > > efimedia: HD(2,GPT,b77a2687-61da-11ed-9652-00a0981073a7,0x800,0x2000000= ) > > rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b > > type: freebsd-swap > > 3. Name: vtbd0p3 > > efimedia: > HD(3,GPT,b7836ca4-61da-11ed-9652-00a0981073a7,0x2000800,0xdfff000) > > rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b > > type: freebsd-zfs > > 1. Name: vtbd0 > > END QUOTE > > > > There is no ESP present in the guest. Instead there is a > > "type: freebsd-boot" partition for which one of the likes of: > > > > # ls -lodT /boot/gpt*boot* > > -r--r--r-- 1 root wheel uarch 62139 Apr 7 15:55:46 2024 /boot/gptboo= t > > -r-xr-xr-x 1 root wheel uarch 109568 Apr 7 15:55:46 2024 > /boot/gptboot.efi > > -r--r--r-- 1 root wheel uarch 176062 Apr 8 01:15:54 2024 > /boot/gptzfsboot > > > > would be in use. None of the 3 support the combination EFI and > > ZFS-for-root-file-system. The only one of those 3 supporting zfs > > is: gptzfsboot > > It is documented to only supports old style BIOS context: > > > > "man 8 gptzfsboot" indicates "gptzfsboot is used on BIOS-based > > computers to boot from a filesystem in a ZFS pool". > > > > gptboot and gptboot.efi only support UFS according to their man > > pages. > > > > If EFI is in use, then the ESP-ish partition is not from the guest > > context but from some place else --unless the man pages are wildly > > wrong about what is supported for the gpt*boot 's. > > > > =3D=3D=3D > > Mark Millard > > marklmi at yahoo.com > > Ah, I've overlooked that. Thanks. > So boot1.efi is not usable here just as gptboot.efi. > gptzfsboot is the only bootcode for freebsd-boot partition on GPT which > supports ZFS, and corresponding loader WAS zfsloader but IIRC ZFS > support IS now incorporated into loader[_lua|_4th]. > Yes. If you are getting the too old error, then there is a preupdate world booting a stable/13 after my change I think. Warner --=20 > Tomoaki AOKI > > --000000000000f03f2d0621935107 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Sep 7, 2024, 9:24=E2=80=AFPM Tomoaki AOKI <= junchoon@dec.sakura.ne.jp&= gt; wrote:
On Sat, 7 Sep 2024 19:52= :53 -0700
Mark Millard <marklmi@yahoo.com> wrote:

> Tomoaki AOKI <junchoon_at_dec.sakura.ne.jp> wrote on
> Date: Sun, 08 Sep 2024 01:54:28 UTC :
>
> > On Sun, 8 Sep 2024 02:01:02 +0100
> > void <void@f-m.fm> wrote:
> >
> > > On Sun, Sep 08, 2024 at 09:23:02AM +0900, Tomoaki AOKI wrote= :
> > >
> > > . . .
> >
> > If not automounted, you can mount ESP manually as msdosfs there, = at
> > least for bare-metal host. IIUC, recent installation by bsdinstal= l
> > creates fstab entry for it by default.
>
> void previously reported:
>
> QUOTE
> # gpart list | grep -E '(Name|type|efi|media)'
> 1. Name: vtbd0p1
> efimedia: HD(1,GPT,b7731537-61da-11ed-9652-00a0981073a7,0x28,0x400) > rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
> type: freebsd-boot
> 2. Name: vtbd0p2
> efimedia: HD(2,GPT,b77a2687-61da-11ed-9652-00a0981073a7,0x800,0x200000= 0)
> rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
> type: freebsd-swap
> 3. Name: vtbd0p3
> efimedia: HD(3,GPT,b7836ca4-61da-11ed-9652-00a0981073a7,0x2000800,0xdf= ff000)
> rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
> type: freebsd-zfs
> 1. Name: vtbd0
> END QUOTE
>
> There is no ESP present in the guest. Instead there is a
> "type: freebsd-boot" partition for which one of the likes of= :
>
> # ls -lodT /boot/gpt*boot*
> -r--r--r--=C2=A0 1 root wheel uarch=C2=A0 62139 Apr=C2=A0 7 15:55:46 2= 024 /boot/gptboot
> -r-xr-xr-x=C2=A0 1 root wheel uarch 109568 Apr=C2=A0 7 15:55:46 2024 /= boot/gptboot.efi
> -r--r--r--=C2=A0 1 root wheel uarch 176062 Apr=C2=A0 8 01:15:54 2024 /= boot/gptzfsboot
>
> would be in use. None of the 3 support the combination EFI and
> ZFS-for-root-file-system. The only one of those 3 supporting zfs
> is: gptzfsboot
> It is documented to only supports old style BIOS context:
>
> "man 8 gptzfsboot" indicates "gptzfsboot is used on BIO= S-based
> computers to boot from a filesystem in a ZFS pool".
>
> gptboot and gptboot.efi only support UFS according to their man
> pages.
>
> If EFI is in use, then the ESP-ish partition is not from the guest
> context but from some place else --unless the man pages are wildly
> wrong about what is supported for the gpt*boot 's.
>
> =3D=3D=3D
> Mark Millard
> marklmi at yahoo.com

Ah, I've overlooked that. Thanks.
So boot1.efi is not usable here just as gptboot.efi.
gptzfsboot is the only bootcode for freebsd-boot partition on GPT which
supports ZFS, and corresponding loader WAS zfsloader but IIRC ZFS
support IS now incorporated into loader[_lua|_4th].
<= /div>

Yes. If you are getting = the too old error, then there is a preupdate world booting a stable/13 afte= r my change I think.

War= ner

--
Tomoaki AOKI=C2=A0 =C2=A0 <junchoon@dec.sakura.ne.jp>

--000000000000f03f2d0621935107--