Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Nov 2023 12:36:51 -0400
From:      mike tancsa <mike@sentex.net>
To:        FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: RELENG_13 to 14 upgrade fail (resolved)
Message-ID:  <82e3580d-3d25-4cfc-8b18-e54a1fddbf12@sentex.net>
In-Reply-To: <0c19b8a6-119c-4f5d-af26-d625afc7afec@sentex.net>
References:  <0c19b8a6-119c-4f5d-af26-d625afc7afec@sentex.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/2/2023 12:28 PM, mike tancsa 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 ?
>
>

A little easier than I though. I just grabbed the 2 files from a 
RELENG_14 image and put them in /tmp on my nfs server where the raw vm 
image is. Then

mdconfig -f problem-vm-image.raw
gpart bootcode -b /tmp/pmbr -p /tmp/gptzfsboot -i 1 md0
mdconfig -d -u 0

and its up and running again

     ---Mike





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82e3580d-3d25-4cfc-8b18-e54a1fddbf12>