Re: 12.0 - (zpool upgrade ) /bootpool/boot/* new location for /boot/* ?

On 12/14/18 4:45 PM, Bruce Cantrall wrote:
> Hi, First time poster.
> Did the location for the files in /boot move to /bootpool/boot but the zpool upgrade did not know this in 12.0?
> 
> # uname -a
> FreeBSD filestore1b.phishline.com 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC  amd64
> 
> # zpool upgrade zroot
> This system supports ZFS pool feature flags.
> 
> Enabled the following features on 'zroot':
>   large_dnode
>   spacemap_v2
> 
> If you boot from pool 'zroot', don't forget to update boot code.
> Assuming you use GPT partitioning and da0 is your boot disk
> the following command will do it:
> 
>                 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0
> 
> ?????????????
> (/boot does not exist but is now in /bootpool/boot)
> 
> #  gpart bootcode -b /bootpool/boot/pmbr -p /bootpool/boot/gptzfsboot -i 1 da0
> 
> (SNIP)
> This system supports ZFS pool feature flags.
> 
> Enabled the following features on 'bootpool':
>   large_dnode
>   spacemap_v2
> 
> # freebsd-update upgrade
> src component not installed, skipped
> Cannot identify running kernel
> 
> Worked Ok when I added the /bootpool directory to the path.

zpool upgrade's message is not very smart.  I think it just uses hardcoded paths
and a hardcode drive.  (For example, it always says da0 even if you have
a mirror in which case you should update the bootcode on all of the devices.)

I have a fresh install of 12.0-RC3 here that still has the files in /boot
and doesn't have a /bootpool directory at all.

-- 
John Baldwin