Re: Loader.conf problem

On 11/21/17 13:04, Warner Losh wrote: > > I think I see the problem... There's no LOADER_SUPPORT_GELI in the > gptzfsboot built. Let me fix that... Seems to be caused by having > HAVE_GPT instead of HAVE_GELI r326069 should get this working again. > Can you confirm this independently. > > Sorr

Re: Loader.conf problem

On Tue, Nov 21, 2017 at 11:53 AM, Thomas Laus wrote: > On 11/21/17 12:38, Andriy Gapon wrote: > > On 21/11/2017 14:48, Thomas Laus wrote: > >> I had boot success when copying gptzfsboot file from my laptop that is > >> running r325474. The problem CURRENT version running on my desktop is > >> r3

Re: Loader.conf problem

On 11/21/17 12:38, Andriy Gapon wrote: > On 21/11/2017 14:48, Thomas Laus wrote: >> I had boot success when copying gptzfsboot file from my laptop that is >> running r325474. The problem CURRENT version running on my desktop is >> r326012. > > could you please compare sizes of the files before goi

Re: Loader.conf problem

On Tue, Nov 21, 2017 at 10:38 AM, Andriy Gapon wrote: > On 21/11/2017 14:48, Thomas Laus wrote: > > I had boot success when copying gptzfsboot file from my laptop that is > > running r325474. The problem CURRENT version running on my desktop is > > r326012. > > Thomas, > > could you please compa

Re: Loader.conf problem

On 21/11/2017 14:48, Thomas Laus wrote: > I had boot success when copying gptzfsboot file from my laptop that is > running r325474. The problem CURRENT version running on my desktop is > r326012. Thomas, could you please compare sizes of the files before going further? -- Andriy Gapon

Re: Loader.conf problem

On 11/20/17 18:46, Warner Losh wrote: > > > On Mon, Nov 20, 2017 at 4:31 PM, Thomas Laus > wrote: > > Warner Losh [i...@bsdimp.com ] wrote: > > > > Can you revert this part of the change? Go back to a known-working > version > > of

Re: Loader.conf problem

On Mon, Nov 20, 2017 at 4:31 PM, Thomas Laus wrote: > Warner Losh [i...@bsdimp.com] wrote: > > > > Can you revert this part of the change? Go back to a known-working > version > > of those files? Let me know if that fixes the problem? Bonus points for > > bisecting which one of the few dozen comm

Re: Loader.conf problem

Warner Losh [i...@bsdimp.com] wrote: > > Can you revert this part of the change? Go back to a known-working version > of those files? Let me know if that fixes the problem? Bonus points for > bisecting which one of the few dozen commits I did that caused this > regression... > > I don't have a G

Re: Loader.conf problem

On Mon, Nov 20, 2017 at 2:42 PM, Thomas Laus wrote: > Warner Losh [i...@bsdimp.com] wrote: > > On Mon, Nov 20, 2017 at 1:30 PM, Thomas Laus wrote: > > > > > I recently upgraded my FreeBSD-Current system today and did not fully > > > understand the impact of changes to loader.conf. My system has

Re: Loader.conf problem

Warner Losh [i...@bsdimp.com] wrote: > On Mon, Nov 20, 2017 at 1:30 PM, Thomas Laus wrote: > > > I recently upgraded my FreeBSD-Current system today and did not fully > > understand the impact of changes to loader.conf. My system has a Geli > > encrypted ZFS pool. In the past whenever I screwed

Re: Loader.conf problem

On Mon, Nov 20, 2017 at 1:30 PM, Thomas Laus wrote: > I recently upgraded my FreeBSD-Current system today and did not fully > understand the impact of changes to loader.conf. My system has a Geli > encrypted ZFS pool. In the past whenever I screwed up, I was able to > use 'Beadm' into boot the

Loader.conf problem

I recently upgraded my FreeBSD-Current system today and did not fully understand the impact of changes to loader.conf. My system has a Geli encrypted ZFS pool. In the past whenever I screwed up, I was able to use 'Beadm' into boot the most recent good kernel or enter a shell to reread the UPDATIN