Date: Thu, 12 Oct 2023 05:34:42 +0100 From: void <void@f-m.fm> To: freebsd-arm@freebsd.org Subject: Re: unable to boot latest 14-stable Message-ID: <ZSd3YuEX3qaYSbC7@int21h> In-Reply-To: <005C6B77-2ED1-4FA9-9A6D-B97FB9E8ADD8@yahoo.com> References: <ZSXPnTXAdSJYrBDX@int21h> <841CA663-55E0-4EAD-B700-66DC884B50FA@yahoo.com> <ZSZotIDLHZE1SzwL@int21h> <ZSZ3vATEEGO3N8-T@int21h> <55C64D6A-2712-408A-B7A7-BA8081CA99FC@yahoo.com> <ZSasPYs3jCZ7Si6U@int21h> <005C6B77-2ED1-4FA9-9A6D-B97FB9E8ADD8@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mark, I think the zpool upgrade thing is a red herring, a symptom of the root cause. On the 30th September the machine was upgraded from 13-stable of that date to 14-stable of that date. When it became 14-stable, zpool was upgraded. In the days between then and 11th October, the machine was rebooted several times, each time it came back up normally. Around the 10-11th October, sources were updated and a new buildworld etc cycle happened, installing a slightly later 14-stable version. The boot failure would seem to indicate the msdos materials needed for booting changed between the 30th Sept and 10-11th October. Either that or something the materials invoke on the zfs side of things. The problem I'm having is that I cannot find anything relevant for this on cgit in the timeframe and there's no mention of anything relevant to this in UPDATING, so I can't anticipate the problem happening again. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZSd3YuEX3qaYSbC7>