Date: Fri, 08 May 2020 10:32:06 -0300 From: Joseph Mingrone <jrm@FreeBSD.org> To: Steve Wills <swills@FreeBSD.org> Cc: questions@freebsd.org, 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: <861rnublih.fsf@phe.ftfl.ca> In-Reply-To: <ac07ac9b-ce3a-ab05-a95f-b1e4c4fd88d2@FreeBSD.org> (Steve Wills's message of "Fri, 8 May 2020 09:13:44 -0400") References: <CANRUcdAtNWdMMoSYmZ27NEFgPQTF7-KFdBXBTy6JmuDxG8edUw@mail.gmail.com> <ac07ac9b-ce3a-ab05-a95f-b1e4c4fd88d2@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
Steve Wills <swills@FreeBSD.org> writes:
> I didn't solve it, I avoided it by renaming the kernel directory and reinstalling the kernel, forcing the bits to be in a different physical
> location on disk... The only theory I had at the time was that the bits were beyond some arbitrary 4G limit or something, but that was just a
> wild idea. Good luck, that's super frustrating.
> Steve
Interesting. Was this with your X220? If so, maybe there is something
up with the BIOS. In case it's useful, this is an X220 with 8 GB RAM.
% zpool status
pool: zroot
state: ONLINE
scan: scrub repaired 0 in 0 days 00:49:21 with 0 errors on Thu May 7 17:30:55 2020
config:
NAME STATE READ WRITE CKSUM
zroot ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ada0p4.eli ONLINE 0 0 0
ada1p4.eli ONLINE 0 0 0
errors: No known data errors
% zpool list
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
zroot 228G 198G 30.0G - - 74% 86% 1.00x ONLINE -
Don't judge me too harshly about the free space. :)
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=zfs:zroot/ROOT/default:` and `boot`, but the same
>> error is shown.
>> Steve and Kyle, did you ever solve this problem?
>> Thanks,
>> Joe
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
iQKkBAEBCgCOFiEEVbCTpybDiFVxIrrVNqQMg7DW754FAl61X1ZfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1
QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUQHGpybUBmcmVl
YnNkLm9yZwAKCRA2pAyDsNbvnsnGD/941NY/WKF2D7cW3Eywy6OxHPFw8v596UCj
HLrpY4TW7HRCO6g/Y/Hl6zhSwbSxMSv5ifFP0Hwww0wEFtkE81heFgSGhy473heI
rqG/8fWkJvMfI27K642ZANmapfYDZ8sGD0/6Y2ZH9HdHLJWcZFc8XGRaOUWcmeY6
RgQ20A/Z5v6m/513IBMeO6nBqEtOSve9eQpY7AU1S518CrvHTM+UWw0G22MwMeNj
IhHgWroOFRhVt24Vv/uZ+9roV7YJxR8YSMObGZVVUPZlC6ydgSC58Q6evA/4hH5n
3tIORL2aYqOLkxncM4W/QQiRXJVbpp3wKbbLbBxybcSiYOXOwhNnWhlj1UZ+GQOU
Is+Za2khYhkLcrEaDSkSHunNHD8VlHnplbdKkRPffoJIlkg9CdhWCLi7heom5DBu
qen72sxyus6mdsqXSoYRaFN1bW3WUKJJVIil2vjam2w6b4VjsLSwKQgPvB5ymcbY
kDe8Gf/QkgER4p5mUZR8dZUniJU2WrrM1uMJ+dtUBTgMzganOAFLXOG/O6kZx7sV
CmvNYKLgr8VzLlSvxR4Sg0CV/51q8EZK591AZgwkSiNabob+/WYLVJknYCHUx6Ac
29PUMqSeSjBp8IExMMjuq6tcxKVzWvJRVJ9FpRpYhaFya2m9urBCqViG46X9iIAi
4bhcSOvb+g==
=Dxyu
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?861rnublih.fsf>
