From owner-freebsd-stable@freebsd.org Sat Dec 14 01:29:52 2019 Return-Path: Delivered-To: freebsd-stable@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 5D2081DD15C for ; Sat, 14 Dec 2019 01:29:52 +0000 (UTC) (envelope-from b@sashk.xyz) Received: from forward501o.mail.yandex.net (forward501o.mail.yandex.net [37.140.190.203]) (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 47ZVML3pqFz3JCQ for ; Sat, 14 Dec 2019 01:29:50 +0000 (UTC) (envelope-from b@sashk.xyz) Received: from mxback7j.mail.yandex.net (mxback7j.mail.yandex.net [IPv6:2a02:6b8:0:1619::110]) by forward501o.mail.yandex.net (Yandex) with ESMTP id 9291C1E800E5; Sat, 14 Dec 2019 04:29:47 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback7j.mail.yandex.net (mxback/Yandex) with ESMTP id nxclsCYb7d-TkrmiOn0; Sat, 14 Dec 2019 04:29:46 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sashk.xyz; s=mail; t=1576286986; bh=fViUyLS6YOuQdazLe7KyA6rQDmugaG5h1uMYZpcdWeA=; h=References:Date:Message-Id:Subject:In-Reply-To:To:From; b=pwFz8E0gfFi7I9PkJGFUzRPZOWpGaKXDpn56Noj/MOAIz/NZmZOTVaWZaxx6mpl5H Tpyutnh9mq03dBAVhHFek+o5SE91xfStK5UHLbL0L7saBsN7X2HABBdb6HmjYSIe69 qj+FezSA6W7gJV4ap8yau1mStYvIQcT/uYLGuYP4= Received: by iva8-03ad76494624.qloud-c.yandex.net with HTTP; Sat, 14 Dec 2019 04:29:46 +0300 From: sashk To: Marc Branchaud , Eugene Grosbein , Mark Martinec , "freebsd-stable@freebsd.org" In-Reply-To: References: <22f5b92a09ea4d62ac3feb74457067f7@ijs.si> <5EEBAFC0-4FA3-4219-A918-7376F4223656@me.com> <0F5FCC70-EADB-4F9E-A391-F1A73BE5608F@me.com> <1543954753.1860.243.camel@freebsd.org> <53ceda24-fa1b-8546-3511-bd500b440dfe@digiware.nl> <4c4019102b63054f8de93324dba0e776@ijs.si> <998f886a-7498-7268-75cf-4e767835db82@grosbein.net> Subject: Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2 MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 13 Dec 2019 20:29:46 -0500 Message-Id: <12248491576286986@iva8-03ad76494624.qloud-c.yandex.net> Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 X-Rspamd-Queue-Id: 47ZVML3pqFz3JCQ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=sashk.xyz header.s=mail header.b=pwFz8E0g; dmarc=none; spf=pass (mx1.freebsd.org: domain of b@sashk.xyz designates 37.140.190.203 as permitted sender) smtp.mailfrom=b@sashk.xyz X-Spamd-Result: default: False [-2.81 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[sashk.xyz:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:37.140.128.0/18]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sashk.xyz]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[sashk.xyz:+]; IP_SCORE(-1.71)[ipnet: 37.140.128.0/18(-4.79), asn: 13238(-3.78), country: RU(0.01)]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_IN_DNSWL_LOW(-0.10)[203.190.140.37.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13238, ipnet:37.140.128.0/18, country:RU]; RCVD_TLS_LAST(0.00)[]; SUSPICIOUS_RECIPS(1.50)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2019 01:29:52 -0000 I hit this issue about year ago and Toomas Soome was able to figure out what was causing this and fixed in the https://svnweb.freebsd.org/base?view=revision&revision=342151 I believe this got into 12.1. -Aleks 13.12.2019, 15:59, "Marc Branchaud" : > On 2019-12-10 10:16 p.m., Eugene Grosbein wrote: >>  10.12.2019 23:08, Mark Martinec пишет: >>>  2019-12-10 16:35, Marc Branchaud wrote: >>> >>>>  On 2019-12-10 9:18 a.m., Mark Martinec wrote: >>>>>  Commenting on a thread from 2018-12 and from 2019-09-20, with my solution >>>>>  to the boot problem at the end, in case anyone is still interested. >>>> >>>>  Thank you very much for this. A couple of questions: >>>> >>>>  (1) Why do you say "raw devices for historical reasons"? Glancing >>>>  through the zpool man page and the Handbook, I see nothing >>>>  recommending or requiring GPT partitions. >>> >>>  Apparently using raw devices for zpool is now discouraged, >>>  although I don't think it has ever become officially unsupported. >> >>  Loader bugs do not mean that "using raw devices for zpool is now discouraged". > > Glad to hear that! > > Should there be a PR for this issue? (A quick Bugzilla search for > "zpool gpt boot" found nothing...) > >                 M. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"