Ran gpart bootcode ... now system won't boot

[Bob Willcox]

Well, I wound up having to reinstall my system since the BIOS didn't recognize
the drive as being bootable following the gpart bootcode update. I'm going to
be extremely nervous about ever running that command again.

Bob

On Sat, Nov 07, 2020 at 02:37:45PM +1100, matti k wrote:
> On Fri, 6 Nov 2020 16:07:47 -0600
> Bob Willcox <bob at immure.com> wrote:
> 
> > On Fri, Nov 06, 2020 at 02:35:25PM -0600, Bob Willcox wrote:
> > > Hi All,
> > > 
> > > I believe I just hosed up one of my systems to the point that it no
> > > longer can boot. I updated my zroot zfs pool following an uprade of
> > > the system from 12.1-stable to 12.2-stable. When I did the 'zpool
> > > upgrad zroot' it prompted me to run this command:
> > > 
> > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0
> > > 
> > > So, I adjusted the command to be this since my root is on an nvme
> > > drive:
> > > 
> > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 nvd0
> > > 
> > > That ran ok (no errors) however when I now try to boot the system
> > > it drops into BIOS claiming that there is no boot disk.
> > > 
> > > So, can anyone tell me what I did wrong here and how can I recover
> > > from it?
> > > 
> > > Thanks in advance,
> > > Bob
> > 
> > I noticed that I likely used the wrong index value, 1, when I ran the
> > command as I doubt that that is correct for my drive. I'm not sure
> > since I haven't been able to boot the system from a thumb drive yet
> > (work getting in the way), but will be doing that. Is it likely that
> > updating the wrong partion (wrond index) would cause the BIOS to not
> > find a boot drive?
> > 
> > Thanks,
> > Bob
> 
> Hi Bob
> 
> Is it booting to a mountroot prompt?
> 
> I had a similar issue after upgrading 12.1-RELEASE to 12.2-RELEASE
> using freebsd-update
> 
> It would boot to a mountroot prompt more times than not, you can just
> hit the return key at the mountroot and it will reboot
> 
> I did try upgrading the motherboard (AsRock) BIOS and the bootcode
> using zpool upgrade zroot but this did not help - in my case value 1 is
> efi and value 2 is freebsd-boot so used 2
> 
> What did fix it was going into BIOS setup and changing the first boot
> device from UEFI to the NVMe drive (basically stopped using UEFI boot)
> 
> Cheers,
> Matti

-- 
Bob Willcox    | It's possible that the whole purpose of your life is to
bob at immure.com | serve as a warning to others.
Austin, TX     |