Date: Fri, 08 May 2020 10:32:19 -0300 From: Joseph Mingrone <jrm@FreeBSD.org> To: Toomas Soome <tsoome@me.com> Cc: Steve Wills <swills@FreeBSD.org>, questions@freebsd.org, Kyle Evans <kevans@freebsd.org>, tsoome@freebsd.org, Allan Jude <allanjude@freebsd.org> Subject: Re: ZFS system can no longer boot - zfs_alloc()/zfs_free() mismatch Message-ID: <86zhaia6xo.fsf@phe.ftfl.ca> In-Reply-To: <53F8CCBC-80EA-4CC6-9775-1E50B3D18D4A@me.com> (Toomas Soome's message of "Fri, 8 May 2020 16:18:07 %2B0300") References: <CANRUcdAtNWdMMoSYmZ27NEFgPQTF7-KFdBXBTy6JmuDxG8edUw@mail.gmail.com> <ac07ac9b-ce3a-ab05-a95f-b1e4c4fd88d2@FreeBSD.org> <53F8CCBC-80EA-4CC6-9775-1E50B3D18D4A@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Toomas Soome <tsoome@me.com> writes: >> On 8. May 2020, at 16:13, Steve Wills <swills@FreeBSD.org> 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----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86zhaia6xo.fsf>