From owner-freebsd-questions@freebsd.org Fri May 8 13:32:21 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 213DF2D78B6 for ; Fri, 8 May 2020 13:32:21 +0000 (UTC) (envelope-from jrm@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 49JWTd09Z1z3K86 for ; Fri, 8 May 2020 13:32:21 +0000 (UTC) (envelope-from jrm@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 05C2A2D78B2; Fri, 8 May 2020 13:32:21 +0000 (UTC) Delivered-To: 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 0578E2D78B1 for ; Fri, 8 May 2020 13:32:21 +0000 (UTC) (envelope-from jrm@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49JWTc6H6Cz3K81; Fri, 8 May 2020 13:32:20 +0000 (UTC) (envelope-from jrm@freebsd.org) Received: from phe.ftfl.ca.ftfl.ca (drmons0544w-156-57-163-35.dhcp-dynamic.fibreop.ns.bellaliant.net [156.57.163.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: jrm/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 7605AE29A; Fri, 8 May 2020 13:32:20 +0000 (UTC) (envelope-from jrm@freebsd.org) From: Joseph Mingrone To: Toomas Soome Cc: Steve Wills , questions@freebsd.org, Kyle Evans , tsoome@freebsd.org, Allan Jude Subject: Re: ZFS system can no longer boot - zfs_alloc()/zfs_free() mismatch References: <53F8CCBC-80EA-4CC6-9775-1E50B3D18D4A@me.com> Date: Fri, 08 May 2020 10:32:19 -0300 In-Reply-To: <53F8CCBC-80EA-4CC6-9775-1E50B3D18D4A@me.com> (Toomas Soome's message of "Fri, 8 May 2020 16:18:07 +0300") Message-ID: <86zhaia6xo.fsf@phe.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Mailman-Approved-At: Fri, 08 May 2020 18:19:39 +0000 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.32 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2020 13:32:21 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Toomas Soome writes: >> On 8. May 2020, at 16:13, Steve Wills wrote: >> I didn't solve it, I avoided it by renaming the kernel directory and rei= nstalling the kernel, forcing the bits to be in a different physical locati= on on disk... The only theory I had at the time was that the bits were beyo= nd some arbitrary 4G limit or something, but that was just a wild idea. Goo= d luck, that's super frustrating. >> Steve > I guess we better backport the zfs_alloc/zfs_free removal code=E2=80=A6 = You can use loader from current meanwhile. > rgds, > toomas We tried loader/zfsloader from current, but the got the same error. Joe >> On 5/7/20 7:59 PM, Joseph Mingrone wrote: >>> Hello everyone, >>> As it says in the subject line, my system stopped booting for some >>> unknown reason. It might have been after upgrading from 12.1-p2 to >>> -p4, but I'm unsure. It sounds similar to this issue: >>> https://twitter.com/alelab_/status/1222437570501644291 >>> Allan and I tried debugging for a few hours today, but without >>> success. We tried replacing the boot code and the loaders, but the >>> result was the same. We also tried booting from a usb thumb drive, >>> then `set currdev=3Dzfs:zroot/ROOT/default:` and `boot`, but the same >>> error is shown. >>> Steve and Kyle, did you ever solve this problem? >>> Thanks, >>> Joe --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKkBAEBCgCOFiEEVbCTpybDiFVxIrrVNqQMg7DW754FAl61X2NfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUQHGpybUBmcmVl YnNkLm9yZwAKCRA2pAyDsNbvnnvND/4ww7erb7nYRAqPI2q5x/bvH2D2fQED9Zvx 5ciwnpqtVUy+vVSGFmJPlm95l5xqHSjxYH5U+DtOkGx0Zb/SBRrNEAj8LKzYHNSR mg9l+hk79/9dfh6s8zqOFL3NbTEbnVdxO6dOEu3lXHeaLfuqlQwDU9N8okwZCz9n 4fauylxFsv+VNvnFwgufUlBaFtA09+NQWCYvccTOzJhUnJwPYIcL55rofY315mHP n2B8LPgnsyalPdY5SmLCV50JoSYXJ3DtS9YQG8f8Ieq3CmaUd9C2IMkc+g4RK2DK ReR1hwdkD9czcymoN/LSAkdH6d/R4I0WsXM+CIKHUFngmP3m6u38HOrwEVJJxW4t Xp04V3sRco2XkgTSjb53s80h00tOMA5eEJq1vq8AiLiNCjiwLS781mBdTFWuUMZo uIL38vMFRIcuXw7EYjzNGwDSRtM6i9q8b5ob60gKQVPMIAvDdeZ67cVvs7eq0/2I 5ndfa9KBd+eeQOfQHlJz1qFNIhuhWuuGGBpACcv33sCIWCaXoo8VhIQDR7NrnT/G vWuVp/+Kzg4AQ8WRhhBdrg6qu6D/4SeSCpIZQjpsoXrmBwUQ0GOU4ECNLJxNXJe3 lf/L81TqYAvip2+s1FKM1DvLu8UB9tE+LxJLkOhLgkKqfs1JKTdViB5Vk50gw1Uo +ltkQRgRqg== =wl3a -----END PGP SIGNATURE----- --=-=-=--