From owner-freebsd-bugs@freebsd.org Thu Aug 2 06:56:18 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3BD5105ADFA for ; Thu, 2 Aug 2018 06:56:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 80A6576C8C for ; Thu, 2 Aug 2018 06:56:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 41D25105ADF9; Thu, 2 Aug 2018 06:56:17 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DF74105ADF8 for ; Thu, 2 Aug 2018 06:56:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB10A76C8B for ; Thu, 2 Aug 2018 06:56:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D692724FB5 for ; Thu, 2 Aug 2018 06:56:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w726uF88011510 for ; Thu, 2 Aug 2018 06:56:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w726uF0v011509 for bugs@FreeBSD.org; Thu, 2 Aug 2018 06:56:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229972] 11.2-RELEASE kernel wont boot with zfs mirror root Date: Thu, 02 Aug 2018 06:56:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: freebsd.68fba@nospam.spacesurfer.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 06:56:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229972 --- Comment #4 from Patrick Mackinlay --- Yesterday I had some time to investigate this further and believe I have fo= und the problem (at least for me). I created a bhyve vm and installed a simple vanilla FreeBSD 11.1 instance w= ith a single root ZFS pool (nothing special, single partition, no raid or mirro= r). I then used freebsd-update to bring it up to the latests 11.1 patch level, = this booted fine. After that I used freebsd-update to go to 11.2. No problems. My main desktop (the one that failed the upgrade) has two ZFS pools, a mirr= or for the base OS and a raidz2 pool (on geli partitions) for my data. I copied the two disks I use for my image partition onto two old spare disks. The zfs partitions I copied using the zfs send/receive functionality. The boot partitions I created from scratch and used the boot code (and partcode) fro= m my 11.2 vm install. This is when I noticed that the gptzfsboot code from 11.2 = is different from the 11.1 gptzfsboot code. After a few changes to the vm copi= es (rc.conf had to be modified for the different network, loader.conf vfs.root.mountfrom had to be changed ...). I booted the copy in my vm. I followed the freebsd-update process, but note that my install has a custom kernel, so after the final "freebsd-update install" used the old 11.1 kerne= l. I then built my kernel from source and rebooted the vm. All went well, no iss= ues. So there are 2 things I did different for the true upgrade and the vm upgra= de. 1. I used the latest gptzfsboot code in the vm upgrade 2. I built the custom kernel after the 11.2 base upgrade in the vm. For the= non vm I build the new kernel before the base upgrade and then installed it aft= er the base upgrade One of those two steps fixed the problem. I assume it was using the latest gptzfsboot code that fixed the issue (I always build the new kernel with the old code base (new src) and I have never had problems in the past). So as far as I am concerned this issue is fixed, although it would be nicer= if FreeBSD were a bit more forgiving when you get it wrong. Also I did not see= any note about the gptzfsboot code changing in the UPDATING file. --=20 You are receiving this mail because: You are the assignee for the bug.=