From owner-freebsd-questions@freebsd.org Mon Nov 9 20:40:49 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EA29546CBFD for ; Mon, 9 Nov 2020 20:40:49 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CVNDd19Psz3rsD for ; Mon, 9 Nov 2020 20:40:48 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id 0A9Kefa2061358 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 9 Nov 2020 14:40:41 -0600 (CST) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id 0A9Kee2F061357; Mon, 9 Nov 2020 14:40:40 -0600 (CST) (envelope-from bob) Date: Mon, 9 Nov 2020 14:40:40 -0600 From: Bob Willcox To: matti k Cc: questions list Subject: Re: Ran gpart bootcode ... now system won't boot Message-ID: <20201109204040.GD22730@rancor.immure.com> Reply-To: Bob Willcox References: <20201106203524.GB22730@rancor.immure.com> <20201106220747.GC22730@rancor.immure.com> <20201107143745.110b5059@ws1.wobblyboot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201107143745.110b5059@ws1.wobblyboot.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 4CVNDd19Psz3rsD X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bob@rancor.immure.com has no SPF policy when checking 108.84.10.9) smtp.mailfrom=bob@rancor.immure.com X-Spamd-Result: default: False [-0.77 / 15.00]; HAS_REPLYTO(0.00)[bob@immure.com]; ARC_NA(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[108.84.10.9:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_TLS_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[immure.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.03)[0.026]; SPAMHAUS_ZRD(0.00)[108.84.10.9:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[bob@immure.com,bob@rancor.immure.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7018, ipnet:108.64.0.0/11, country:US]; FROM_NEQ_ENVFROM(0.00)[bob@immure.com,bob@rancor.immure.com]; MAILMAN_DEST(0.00)[freebsd-questions]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2020 20:40:50 -0000 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 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@immure.com | serve as a warning to others. Austin, TX |