Date: Thu, 2 Nov 2023 12:50:54 -0400 From: mike tancsa <mike@sentex.net> To: Xin LI <delphij@gmail.com> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: RELENG_13 to 14 upgrade fail Message-ID: <515d5ad4-9fc8-4f86-936b-b71d8f43d564@sentex.net> In-Reply-To: <CAGMYy3sL%2B2BikO%2BwGakues3aFnUCL=GoEG%2BLdMVF_0gZknpBEg@mail.gmail.com> References: <0c19b8a6-119c-4f5d-af26-d625afc7afec@sentex.net> <CAGMYy3sL%2B2BikO%2BwGakues3aFnUCL=GoEG%2BLdMVF_0gZknpBEg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------5GR0cuQ5jDdf1dJGRHRxpXX7
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
On 11/2/2023 12:39 PM, Xin LI wrote:
>
>
> On Thu, Nov 2, 2023 at 9:28 AM 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=freebsd-boot, p2=freebsd-swap,p3=freebsd-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=efi
p2=freebsd-boot
p3=swap
p4=zfs
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) = 5dcb1e7bc59e5ee7a9bd04faaa20b7ee
MD5 (/mnt/EFI/BOOT/BOOTX64.efi) = 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:~ #
---Mike
--------------5GR0cuQ5jDdf1dJGRHRxpXX7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 11/2/2023 12:39 PM, Xin LI wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGMYy3sL+2BikO+wGakues3aFnUCL=GoEG+LdMVF_0gZknpBEg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default"
style="font-family:monospace,monospace"><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Nov 2, 2023 at
9:28 AM mike tancsa <<a href="mailto:mike@sentex.net"
moz-do-not-send="true" class="moz-txt-link-freetext">mike@sentex.net</a>>
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">On
one of my VMs that I upgraded from RELENG_13 to RELENG_14, I
forgot <br>
to update the boot loader so now at bootup, I have<br>
ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2<br>
<br>
Can't find /boot/zfsloader<br>
<br>
What is the best way to recover from this ? Its a raw vm
image. gpart is <br>
p1=freebsd-boot, p2=freebsd-swap,p3=freebsd-zfs<br>
<br>
I was thinking perhaps start up a second vm thats RELENG_14,
mdconfig <br>
the image, and then what do I need to do ? Just<br>
<br>
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 md0 ?<br>
</blockquote>
<div><br>
</div>
<div>
<div class="gmail_default"
style="font-family:monospace,monospace">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.</div>
</div>
<div class="gmail_default"
style="font-family:monospace,monospace"><br>
</div>
<div class="gmail_default"
style="font-family:monospace,monospace">BTW. pmbr is very
simple and doesn't change that often, updating gptzfsboot
should be sufficient.</div>
<br>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>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 <br>
p1=efi<br>
p2=freebsd-boot<br>
p3=swap<br>
p4=zfs<br>
</p>
<p><br>
</p>
<p>root@zoo2:~ # mount_msdosfs /dev/ada8p1 /mnt<br>
root@zoo2:~ # ls -lR /mnt/EFI/<br>
total 2<br>
drwxr-xr-x 1 root wheel 512 Feb 1 2021 BOOT<br>
drwxr-xr-x 1 root wheel 512 Nov 21 2020 freebsd<br>
<br>
/mnt/EFI/BOOT:<br>
total 1747<br>
-rwxr-xr-x 1 root wheel 894464 Feb 1 2021 BOOTX64.efi<br>
<br>
/mnt/EFI/freebsd:<br>
total 1747<br>
-rwxr-xr-x 1 root wheel 894464 Feb 1 2021 loader.efi<br>
root@zoo2:~ # <br>
<br>
They appear to be the same. Do I just replace both those files ?</p>
<p>root@zoo2:~ # find /mnt -type f | xargs md5<br>
MD5 (/mnt/EFI/freebsd/loader.efi) =
5dcb1e7bc59e5ee7a9bd04faaa20b7ee<br>
MD5 (/mnt/EFI/BOOT/BOOTX64.efi) = 5dcb1e7bc59e5ee7a9bd04faaa20b7ee<br>
root@zoo2:~ # <br>
</p>
<p>with</p>
<p>root@zoo2:~ # ls -l /boot/loader.efi <br>
-r-xr-xr-x 2 root wheel 659968 Oct 31 13:02 /boot/loader.efi<br>
root@zoo2:~ # <br>
</p>
<p> ---Mike<br>
</p>
</body>
</html>
--------------5GR0cuQ5jDdf1dJGRHRxpXX7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?515d5ad4-9fc8-4f86-936b-b71d8f43d564>