All the examples I've seen for updating bootcode assume GPT. If one has MBR (as I do) and assuming the following basic scheme:
gpart show ada0 => 63 976773105 ada0 MBR (466G) 63 976773105 1 freebsd [active] (466G) gpart show ada0s1 => 0 976773105 ada0s1 BSD (466G) 0 943218736 1 freebsd-zfs (450G) 943218736 33554369 2 freebsd-swap (16G) would the equivalent bootcode statement be: gpart bootcode -b /boot/pmbr -p /boot/zfsboot ada0s1 where the boot code is /boot/zfsboot (rather than /boot/gptzfsboot) and ada0s1 is the slice on which FreeBSD is installed? Thanks. On Fri, Dec 27, 2013 at 9:33 AM, Mathieu Arnold <m...@freebsd.org> wrote: > +--On 27 décembre 2013 12:26:49 +0100 Zenny <garbytr...@gmail.com> wrote: > | On 12/27/13, Mathieu Arnold <m...@freebsd.org> wrote: > |> +--On 27 décembre 2013 00:42:36 +0100 Zenny <garbytr...@gmail.com> > |> wrote: > |> | Much awaited release, thanks!. However, does the freebsd-update from > |> | the earlier version bork in case of ZFS on Root? Or is there a safe > |> | way to upgrade without borking. I had a very bad experience when I > |> | upgraded from FreeBSD-10B3 to RC1. Thanks! > |> > |> I upgraded from 9.2 to 10.0-RC1, 10.0-RC2 and 10.0-RC3 with > |> freebsd-update using zfs only boxes, never had any problem. The only > |> thing is, if you run zpool upgrade, do remember to do what it tells you > |> about updating the bootcode. > |> > | > | In my case, I didn't receive any instructions to update the bootcode > | and the bug was acknowledged by the developer. > | > | However, can you tell me exactly what did you do exactly to update the > | bootcode? Appreciate it! > > Well, when you run : > # zpool upgrade yourpool > > it will not print a lot of things, but it will end with : > > If you boot from pool 'yourpool', 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 > > All you have to do is adapt it to run your particular setup, replacing da0 > with the correct disk (and running it for each disk where your pool is, in > my case, it was mfid0 and mfid1.) > > -- > Mathieu Arnold > _______________________________________________ > firstname.lastname@example.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"