Re: RELENG_13 to 14 upgrade fail (resolved)

> On Nov 3, 2023, at 12:36 AM, mike tancsa <mike@sentex.net> wrote:
> 
> 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

For the UEFI boot, the process to upgrade the boot loader is different.

I once made a mistake (I forgot the VM is UEFI bios), and overwrite the total ESP partition, then the VM refused to boot (certainly).
So probably we want a SMART hint when upgrading zfs pool is done.

> mdconfig -d -u 0
> 
> and its up and running again
> 
>     ---Mike

Best regards,
Zhenlei