From owner-freebsd-current@freebsd.org Mon Apr 29 19:24:55 2019 Return-Path: Delivered-To: freebsd-current@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 D2DE2159A82C for ; Mon, 29 Apr 2019 19:24:54 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5C1516D8A7 for ; Mon, 29 Apr 2019 19:24:53 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1556565890; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=PsznsQoInAORYe6+Jrc6Kh6Uib4pZZP+YQkOdOI1JuE6MPSwCHJDvLykcPqXYozKaqyI/oyh/rVOA J4FOLtNwlfCGx0LqZwv/WKDSMZCp7QMHoFadryzW8HF7MhKQpHHdYocvmL74+JouNGG0hflGdZfiAs 0pFi9bNh6U31fpapkBe0gK04jlcnE+V6E+0rq5mR9qDVwZNZ1f2TiDB463ep6i2JdUD5zORqKJywv2 l7C3GUmzBTYCjybewdXZpbXyrW1JhEf12pwdDxvpEbwYY09xVPiXmxMawDftmNNUheKLnC2/MSUALL 0u5HUuHVFYKmPvrrYaSahDdEniW683g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=P2s1iQ2Ixlnf390+kaMu+70/LYmGaJirr1HJuivOCZ8=; b=fy3JOpCOrbZ1owGDHbR5lHOjhMlFD/OsiV7sgZ6PF4STcRMXI5VKx8Tf02eOjrDb5So6xKaKNWiGK CU9Hv96fVZIpGek6t5i1oz6gQayvnrFf7/yZn06g4ZmlHJEf4gL3hzK8X+0VcJikRS2Ogrd+wEMerv CS0lDmWkiFYR0a6lxSR/zflsO3XYQrM7LGgBvAdZLPMXNxPeOnLbFqwDCLyK/qL57equ0fFPXcI8lL J+uygKP5OxhgUN6q9CjvHRjvhLb8ZtF8UuCDZcrKfBX/v29EWLfmj9ZFquMLgs2O/dBDjohkg5GkgH D73C9GSwzjwNJcq21eaeEjpzPLLegng== ARC-Authentication-Results: i=1; outbound2.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=P2s1iQ2Ixlnf390+kaMu+70/LYmGaJirr1HJuivOCZ8=; b=XLfJ/uhCblk0llTku2zOPyG2nT/uaOI9G2P8Z2w72yCOizSVM8+tzW6acG0nuTFUJ+WL7n59CPOUv CjIIQEh6+QnZW9ZF6BbX96K00lBLl1EVlxizuvBWnSIDqTHR6VdVVEN4duZwWjvJtY6DkKIV0GIeDg kr9tvwkSFH8AMkE/VYqH0DRlvP/zxIrbQow4CemkG5FB5RmJuk+x24RFHBQDYl2NcSfWliv7w5d1a5 X+vW+d8EsUbmSnMfjjVoTwI1RJOlW7n5TEixzGInLsJtnIp+0ZC4X51xHfQlpi3J4RQRnO+HNQH4qe 0NgastnIWlnB32WXSn3CV0ebpe7tgRg== X-MHO-RoutePath: aGlwcGll X-MHO-User: 72c72bdd-6ab4-11e9-803b-31925da7267c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.eu.mailhop.org (Halon) with ESMTPSA id 72c72bdd-6ab4-11e9-803b-31925da7267c; Mon, 29 Apr 2019 19:24:48 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x3TJOkBc004100; Mon, 29 Apr 2019 13:24:46 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <6e0db2b2130555acb64c9016a33da07bb0d16f96.camel@freebsd.org> Subject: Re: Question about 'gptzfsboot' From: Ian Lepore To: lausts@acm.org, FreeBSD Current Date: Mon, 29 Apr 2019 13:24:45 -0600 In-Reply-To: <9ed708cc-8b16-12e7-9119-aeebb412317c@acm.org> References: <01d10a11-49b2-2982-01cb-b49a0831d30b@acm.org> <5de29e0b5228d7eb0aac8e0eec116896f11ea862.camel@freebsd.org> <5bf88341-80f0-3aff-f51a-0b1975530f2e@acm.org> <0848043e68641ea47b918b8480ac8a5a3bb773e0.camel@freebsd.org> <940cbef4-67a9-1f8e-2bca-35b41e4a08f9@acm.org> <9ed708cc-8b16-12e7-9119-aeebb412317c@acm.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 5C1516D8A7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.991,0]; ASN(0.00)[asn:16509, ipnet:52.58.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2019 19:24:55 -0000 On Mon, 2019-04-29 at 14:47 -0400, Thomas Laus wrote: > On 2019-04-29 14:27, Thomas Laus wrote: > > It was more than a broken console. All of the other 2 computers > > that I > > upgraded to r346885 were essentially 'dead'. I could not even > > remotely > > login to them via ssh. All of them required a hard power button > > reset > > to get into single user mode to let me comment out the rc.conf line > > that > > loads the DRM driver. The computer could successfully boot without > > DRM > > activation but would go to a black console screen again with > > 'startx'. > > This also required a hard power button shutdown. I rolled back to > > r346544 and everything worked again like before. > > > > My disastrous update to r346885 included installing a new > > gptzfsboot and > > pmbr in the drive boot record. I did not try booting an older > > kernel > > using the new gptzfsboot. I was concerned about the lack of ssh > > login > > when the computers lost their console, so I just rolled back my > > system > > to the last snapshot made a week ago. > > > > Ian: > > I re-activated the r346885 BEADM snapshot and booted from my > 'kernel.old' from r346544 and everything came up OK including 'X'. > > I don't know what that means. It might be that I have a DRM issue > instead of a gptzfsboot problem? Everything except for the kernel is > now running CURRENT r346885. I am not using the updated > drm-current-kmod because I am using the r346544 kernel.old. > > Tom > > I can't say anything at all about drm or other video driver issues, I'm just not knowledgeable about that stuff at all. The only thing I was getting at was that the changes I made in r346675 might make this error stop happening: gptzfsboot: error 1 LBA 18446744072709551608 gptzfsboot: error 1 LBA 1 gptzfsboot: No ZFS pools located, can't boot Emphasis on the "might"... that appears to be an error during probing for zfs, and I made some fixes related to probing for zfs. -- Ian