From nobody Thu Nov 2 17:12:03 2023 X-Original-To: freebsd-stable@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 4SLr5t5kF1z4ytl5 for ; Thu, 2 Nov 2023 17:12:18 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (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 4SLr5t3PnXz3LKj for ; Thu, 2 Nov 2023 17:12:18 +0000 (UTC) (envelope-from delphij@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-9ae2cc4d17eso195368066b.1 for ; Thu, 02 Nov 2023 10:12:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698945136; x=1699549936; 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=kqEZ0zDmDOPJFN3KmkA7kE55UQBxuT/UyoaHAXsM+ps=; b=j4KHHjol7ZkgvsuAI+wOqt6Q7YQ1g3DYsqFOiXUJMUpNmiYBCFX2g9lpIzXD3067Ak 5d9NmGbrtAEHWzwjcTtPSlg8E6jT8pF8ZRqXiaNgPEwvtARyDR7vBjG4/s7SUPiXHLDx QH8MeMLEqamu62d6fXokKSyYfTra0Je6lX/IRqJRUnpZWLnHFhbplRofWD9WI+BlYBje suynojjEPPHDJ+keURUHS1ohW8sqwbRPL46ocAueVXUMag1RhOcmEcwHOsJf38m5d/t8 ta5FdNBYtckiIL8e4i1U/Ke0XSkP7dzfq/1teBksnn3oa65Vd8TgJPI6w4sp0ZJbb3Mf t9SQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698945136; x=1699549936; 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=kqEZ0zDmDOPJFN3KmkA7kE55UQBxuT/UyoaHAXsM+ps=; b=NDVrclXHtg2j5DHCwo69JiAmPS3yGPoporfTJjK+pMIQzzKnGWpXXFHxfZ1MySx6AJ vubBN1daOPIqYl2NwOzSK9yBjuPdwZH37rzrsLxumIsMTa0ZqWpGcDM8BXLuXn1PvfI3 jI5ktV4xkWAllOEhbNSdaBI4S5wBHLe708Vd1xLO6AzrMvg0+NYMqawoTouc04Oh0p1k wkUtE8flcwqsbb1GddRxl9F1Bz085lT7KPxFPt+RXbm9kJkbdhR5UvS093rh734RXZuD 8mhr1mjXnTX2ERRMnUUyOIaPlH1bW5QY1GcivNhfaKe1Op5xYDVIhMVs8PmGNrcdjkZO Y0Qw== X-Gm-Message-State: AOJu0YzNmjCRfn877UMspfWyfr4uF8UoMIms76GW1LdRvZBoOFZekfzY ZJVvvDd60iggjIF7OMKw/qVFo/xMdnOZybeieiY= X-Google-Smtp-Source: AGHT+IGp+jiIMcojUvjVieY6Z+/sCPFXaOfofJsRKbdzzXLNIO1rTHJgMEmhOj/LuKWAV432A1FUaGPfUfUCFuBJ9tw= X-Received: by 2002:a17:907:7b99:b0:9be:30c2:b8fd with SMTP id ne25-20020a1709077b9900b009be30c2b8fdmr5742279ejc.66.1698945135486; Thu, 02 Nov 2023 10:12:15 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <0c19b8a6-119c-4f5d-af26-d625afc7afec@sentex.net> <515d5ad4-9fc8-4f86-936b-b71d8f43d564@sentex.net> In-Reply-To: <515d5ad4-9fc8-4f86-936b-b71d8f43d564@sentex.net> From: Xin LI Date: Thu, 2 Nov 2023 10:12:03 -0700 Message-ID: Subject: Re: RELENG_13 to 14 upgrade fail To: mike tancsa Cc: FreeBSD-STABLE Mailing List Content-Type: multipart/alternative; boundary="0000000000004b2bde06092e7d5a" 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:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4SLr5t3PnXz3LKj --0000000000004b2bde06092e7d5a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Nov 2, 2023 at 9:50=E2=80=AFAM mike tancsa wrote: > On 11/2/2023 12:39 PM, Xin LI wrote: > > > > On Thu, Nov 2, 2023 at 9:28=E2=80=AFAM mike tancsa wrot= e: > >> On one of my VMs that I upgraded from RELENG_13 to RELENG_14, I forgot >> to update the boot loader so now at bootup, I have >> ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 >> >> Can't find /boot/zfsloader >> >> What is the best way to recover from this ? Its a raw vm image. gpart is >> p1=3Dfreebsd-boot, p2=3Dfreebsd-swap,p3=3Dfreebsd-zfs >> >> I was thinking perhaps start up a second vm thats RELENG_14, mdconfig >> the image, and then what do I need to do ? Just >> >> gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 md0 ? >> > > Yes, note that if the host is running FreeBSD you can mdconfig the image > on the host directly and do it on the host too. > > BTW. pmbr is very simple and doesn't change that often, updating > gptzfsboot should be sufficient. > > > Thanks! Another server I have (zoo) is EFI. I have not upgraded the boot > pool yet, but its a mirror (ada8 and ada9). Both are > p1=3Defi > p2=3Dfreebsd-boot > p3=3Dswap > p4=3Dzfs > > > root@zoo2:~ # mount_msdosfs /dev/ada8p1 /mnt > root@zoo2:~ # ls -lR /mnt/EFI/ > total 2 > drwxr-xr-x 1 root wheel 512 Feb 1 2021 BOOT > drwxr-xr-x 1 root wheel 512 Nov 21 2020 freebsd > > /mnt/EFI/BOOT: > total 1747 > -rwxr-xr-x 1 root wheel 894464 Feb 1 2021 BOOTX64.efi > > /mnt/EFI/freebsd: > total 1747 > -rwxr-xr-x 1 root wheel 894464 Feb 1 2021 loader.efi > root@zoo2:~ # > > They appear to be the same. Do I just replace both those files ? > > root@zoo2:~ # find /mnt -type f | xargs md5 > MD5 (/mnt/EFI/freebsd/loader.efi) =3D 5dcb1e7bc59e5ee7a9bd04faaa20b7ee > MD5 (/mnt/EFI/BOOT/BOOTX64.efi) =3D 5dcb1e7bc59e5ee7a9bd04faaa20b7ee > root@zoo2:~ # > > with > > root@zoo2:~ # ls -l /boot/loader.efi > -r-xr-xr-x 2 root wheel 659968 Oct 31 13:02 /boot/loader.efi > root@zoo2:~ # > > Yes, for EFI you mount the EFI ESP (which is a msdosfs) and replace the BOOTX64.efi with latest /boot/loader.efi , then umount the EFI ESP. It's generally a good idea to have access to the physical system, or via a remote console that allows you to mount a .iso image, by the way. Cheers, --0000000000004b2bde06092e7d5a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Nov 2, 2023 at 9:50=E2=80= =AFAM mike tancsa <mike@sentex.net> wrote:
= =20 =20 =20
On 11/2/2023 12:39 PM, Xin LI wrote:
=20


On Thu, Nov 2, 2023 at 9:28=E2=80=AFAM mike tancsa <mike@sentex.net> wrote:
On one of my VMs that I upgraded from RELENG_13 to RELENG_14, I forgot
to update the boot loader so now at bootup, I have
ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2

Can't find /boot/zfsloader

What is the best way to recover from this ? Its a raw vm image. gpart is
p1=3Dfreebsd-boot, p2=3Dfreebsd-swap,p3=3Dfreebsd-zfs

I was thinking perhaps start up a second vm thats RELENG_14, mdconfig
the image, and then what do I need to do ? Just

gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 md0 ?

Yes, note that i= f the host is running FreeBSD you can mdconfig the image on the host directly and do it on the host too.

BTW. pmbr is very simple and doesn't change that often, updating gptzfsboot should be sufficient.


Thanks!=C2=A0 Another server I have (zoo) is EFI. I have not upgrade= d the boot pool yet, but its a mirror (ada8 and ada9). Both are
p1=3Defi
p2=3Dfreebsd-boot
p3=3Dswap
p4=3Dzfs


root@zoo2:~ # mount_msdosfs /dev/ada8p1 /mnt
root@zoo2:~ # ls -lR /mnt/EFI/
total 2
drwxr-xr-x=C2=A0 1 root wheel 512 Feb=C2=A0 1=C2=A0 2021 BOOT
drwxr-xr-x=C2=A0 1 root wheel 512 Nov 21=C2=A0 2020 freebsd

/mnt/EFI/BOOT:
total 1747
-rwxr-xr-x=C2=A0 1 root wheel 894464 Feb=C2=A0 1=C2=A0 2021 BOOTX64.e= fi

/mnt/EFI/freebsd:
total 1747
-rwxr-xr-x=C2=A0 1 root wheel 894464 Feb=C2=A0 1=C2=A0 2021 loader.ef= i
root@zoo2:~ #

They appear to be the same.=C2=A0 Do I just replace both those files = ?

root@zoo2:~ # find /mnt -type f | xargs md5
MD5 (/mnt/EFI/freebsd/loader.efi) =3D 5dcb1e7bc59e5ee7a9bd04faaa20b7ee
MD5 (/mnt/EFI/BOOT/BOOTX64.efi) =3D 5dcb1e7bc59e5ee7a9bd04faaa20b7ee<= br> root@zoo2:~ #

with

root@zoo2:~ # ls -l /boot/loader.efi
-r-xr-xr-x=C2=A0 2 root wheel 659968 Oct 31 13:02 /boot/loader.efi root@zoo2:~ #

Yes, for EFI you mount the EFI ESP (which is= a msdosfs) and replace the BOOTX64.efi with latest /boot/loader.efi , then= umount the EFI ESP.

It's generally a good idea to have access t= o the physical system, or via a remote console that allows you to mount a .= iso image, by the way.

Cheers,
--0000000000004b2bde06092e7d5a--