From owner-freebsd-bugs@freebsd.org Fri May 31 08:13:11 2019 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 167D315B5E1D for ; Fri, 31 May 2019 08:13:11 +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 9CDE088554 for ; Fri, 31 May 2019 08:13:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5B8FF15B5E1C; Fri, 31 May 2019 08:13:10 +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 1AB6415B5E1B for ; Fri, 31 May 2019 08:13:10 +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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 97AC388553 for ; Fri, 31 May 2019 08:13:09 +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 C1E44F2C4 for ; Fri, 31 May 2019 08:13:08 +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 x4V8D8RN063551 for ; Fri, 31 May 2019 08:13:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4V8D8hK063550 for bugs@FreeBSD.org; Fri, 31 May 2019 08:13:08 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 238257] zfsloader: 11.2-STABLE r345498 to r347183 update leaves unbootable system Date: Fri, 31 May 2019 08:13:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bennett@sdf.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: 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.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2019 08:13:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238257 Bug ID: 238257 Summary: zfsloader: 11.2-STABLE r345498 to r347183 update leaves unbootable system Product: Base System Version: 11.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: bennett@sdf.org CC: bennett@sdf.org After installing the new r347183 kernel and rebooting, the new kernel appea= red to be working, so I proceeded to do the mergemaster -p -F, make installworl= d, mergemaster -F, reboot sequence. After entering the GELI passphrase for the boot pool primary device, I got a message beginning with "BTX" followed by several lines of hexadecimal with spaces interspersed. I got help from ano= ther subscriber to the freebsd-stable list, a suggestion to wait one second after entering the GELI passphrase, then hit space. This action resulted in a pr= ompt showing the path to the broken zfsloader and allowing entry of a different path. I entered the same with ".old" appended, and that got me a boot menu= .=20 Once the system was running, I renamed the broken zfsloader to zfsloader.bad.r347183 and renamed zfsloader.old to zfsloader and added a ha= rd link to it called zfsloader.good.r345498. I then reactivated the r345498 b= oot environment and eventually, after further exploration, rebooted, so I am currently back to running r345498. Since reverting, I have continued to update my source tree, but have not bothered to run a "make buildworld" because I have seen no further updates = to either loader or zfsloader from r347183 through r348441. IOW, I cannot upd= ate my FreeBSD system any further until this bug is fixed unless I want to implement a local addition to the updating procedure to add steps to reinst= all a working-but-outdated copy of zfsloader after the "make installworld" step= and remember to do that without fail for every update. For the unsuspecting, but affected, FreeBSD user, who may not know how to g= et the second-stage boot code to ask for a new path to a working boot loader (= as I did not), it would be unconscionable to release 11.3 before zfsloader is fi= xed. I do not know whether loader is similarly broken. I consider such a bug to be of a severity just less than critical because t= here is a way to get the system booted *provided* one knows the trick. I have n= ot seen this trick documented anywhere, and I remain grateful to crahman Ta gm= ail for responding to my plea for help on the -stable list with the instructions for that trick. IMO, the trick should be included and *highlighted* in the Handbook's instructions for updating from source. --=20 You are receiving this mail because: You are the assignee for the bug.=