On 12/15/17 18:37, Warner Losh wrote:
>
> I believe that these issues have been corrected in r326888. My
> refactoring to make it easier to bring in the lua boot loader in r326593
> (after breaking the build in r326584 accidentally) uncovered some latent
> subtle ordering issues. This cause GELI-e
On Wed, Dec 6, 2017 at 8:54 AM, Warner Losh wrote:
>
>
> On Wed, Dec 6, 2017 at 8:35 AM, Thomas Laus wrote:
>
>> Group:
>>
>> I updated my amd64 computer today to r326622 and copied the
>> /boot/gptzfsboot file to each of my ZFS hard drives p1 partition. The
>> BTX loader stopped and could not
On Wed, Dec 06, 2017 at 10:35:37AM -0500, Thomas Laus wrote:
> Group:
>
> I updated my amd64 computer today to r326622 and copied the
> /boot/gptzfsboot file to each of my ZFS hard drives p1 partition. The
> BTX loader stopped and could not load. This rendered my system
> 'un-bootable'. I copie
Toomas Soome [tso...@me.com] wrote:
>
>
> With BIOS boot you can try to press key (space or anything else except enter)
> - if boot1 is good, you will get boot: prompt.
>
BTX fails a long time before boot1 is read. I don't even get a prompt
for my Geli password.
Tom
--
Public Keys:
PGP KeyID
Warner Losh [i...@bsdimp.com] wrote:
> OK. I don't recall seeing a screen shot of the entire boot. Can you send
> that too (privately if you like) so I know exactly what's failing? Is it
> gptzfsboot loading /boot/loader? Is it early in /boot/laoder or
>
It is failing with a hex dump with a BT
> On 9 Dec 2017, at 19:56, Warner Losh wrote:
>
> On Sat, Dec 9, 2017 at 7:12 AM, Thomas Laus wrote:
>
>> On 12/08/17 22:06, Warner Losh wrote:
>>>
>>> Clean build?
>>>
>> It was a clean build. I performed a rm -rf /usr/obj/* before starting
>> the buildworld after cvs updating to r326720.
On Sat, Dec 9, 2017 at 7:12 AM, Thomas Laus wrote:
> On 12/08/17 22:06, Warner Losh wrote:
> >
> > Clean build?
> >
> It was a clean build. I performed a rm -rf /usr/obj/* before starting
> the buildworld after cvs updating to r326720.
>
> A couple of notes on my hardware:
>
> I am not using UEF
On 12/08/17 22:06, Warner Losh wrote:
> Clean build?
>
Here is the contents of my loader.conf:
loader_logo="beastie" #Desired logo:orbbw, orb, fbsdbw, beastiebw, beastie, none
aesni_load="YES"
geom_eli_load="YES"
kern.geom.label.disk_ident.enable="0"
kern.geom.label.gptid.enable="0"
zfs_load="YES"
On 12/08/17 22:06, Warner Losh wrote:
>
> Clean build?
>
It was a clean build. I performed a rm -rf /usr/obj/* before starting
the buildworld after cvs updating to r326720.
A couple of notes on my hardware:
I am not using UEFI and my CPU is an early Intel i5 Skylake that has the
Silicon Debug f
On Fri, Dec 8, 2017 at 7:31 PM, Thomas Laus wrote:
> Warner Losh [i...@bsdimp.com] wrote:
> > Looks like -DEFI_ZFS_BOOT was dropped from boot1.c in r326589. I've
> fixed
> > it in r326714.
> >
> Warren:
>
> I just completed a buildworld on r326720 and it failed to boot again
> with a hex dump an
Warner Losh [i...@bsdimp.com] wrote:
> Looks like -DEFI_ZFS_BOOT was dropped from boot1.c in r326589. I've fixed
> it in r326714.
>
Warren:
I just completed a buildworld on r326720 and it failed to boot again
with a hex dump and BTX failure. I can take a photograph and post it
somewhere of the h
Looks like -DEFI_ZFS_BOOT was dropped from boot1.c in r326589. I've fixed
it in r326714.
Warner
On Thu, Dec 7, 2017 at 5:44 AM, Thomas Laus wrote:
> On 12/06/17 19:38, Warner Losh wrote:
> >
> > OK. Still a fair number of changes, including changes to geli to fix
> > warnings...
> >
> > 326585
On 12/06/17 19:38, Warner Losh wrote:
>
> OK. Still a fair number of changes, including changes to geli to fix
> warnings...
>
> 326585-326594 is a flurry of changes. Then another in the 326609-326610
> range. There's one other trivial one. I'd wager that if '500 works, the
> breakage will be som
> Warner Losh [i...@bsdimp.com] wrote:
> > > > You can just build the boot blocks at each step if you'd like to save
> > > > some time on the binary search.
> > > >
> > > > cd stand
> > > > make cleandir obj depend
> > > > make -j XX
> > > > sudo -E make install
> > > >
> >
> > OK. Still a fair nu
Warner Losh [i...@bsdimp.com] wrote:
> > > You can just build the boot blocks at each step if you'd like to save
> > > some time on the binary search.
> > >
> > > cd stand
> > > make cleandir obj depend
> > > make -j XX
> > > sudo -E make install
> > >
>
> OK. Still a fair number of changes, inclu
On Wed, Dec 6, 2017 at 5:17 PM, Thomas Laus wrote:
> Warner Losh [i...@bsdimp.com] wrote:
> > You can just build the boot blocks at each step if you'd like to save
> some
> > time on the binary search.
> >
> > cd stand
> > make cleandir obj depend
> > make -j XX
> > sudo -E make install
> >
> War
Warner Losh [i...@bsdimp.com] wrote:
> You can just build the boot blocks at each step if you'd like to save some
> time on the binary search.
>
> cd stand
> make cleandir obj depend
> make -j XX
> sudo -E make install
>
Warren:
I built and loaded r326500 successfully. It looks like the problem
Warner Losh [i...@bsdimp.com] wrote:
>
> You can just build the boot blocks at each step if you'd like to save some
> time on the binary search.
>
> cd stand
> make cleandir obj depend
> make -j XX
> sudo -E make install
>
> should suffice. There's no compiler dependency that I'm aware of.
>
I h
On Wed, Dec 6, 2017 at 3:21 PM, Thomas Laus wrote:
> Warner Losh [i...@bsdimp.com] wrote:
> > I've been *VERY* busy between then and now cleaning up the boot loader
> > "accumulated technical debt". Alas, sounds like I've broken something.
> So I
> > think it's a binary search: I'd start with 326
Warner Losh [i...@bsdimp.com] wrote:
> I've been *VERY* busy between then and now cleaning up the boot loader
> "accumulated technical debt". Alas, sounds like I've broken something. So I
> think it's a binary search: I'd start with 326370 as the pivot and 326500 /
> 326250 as the next steps if it
Warner Losh [i...@bsdimp.com] wrote:
> I've been *VERY* busy between then and now cleaning up the boot loader
> "accumulated technical debt". Alas, sounds like I've broken something. So I
> think it's a binary search: I'd start with 326370 as the pivot and 326500 /
> 326250 as the next steps if it
On Wed, Dec 6, 2017 at 9:48 AM, Thomas Laus wrote:
> Warner Losh [i...@bsdimp.com] wrote:
> >
> > Any chance you can bisect when this happened? I think I'll need more
> > details to see what happened. What was your old loader that world based
> on?
> >
> My last good gptzfsboot was r326070. I ha
Warner Losh [i...@bsdimp.com] wrote:
>
> Any chance you can bisect when this happened? I think I'll need more
> details to see what happened. What was your old loader that world based on?
>
My last good gptzfsboot was r326070. I had not built anything since
then until this morning when I built w
On Wed, Dec 6, 2017 at 8:35 AM, Thomas Laus wrote:
> Group:
>
> I updated my amd64 computer today to r326622 and copied the
> /boot/gptzfsboot file to each of my ZFS hard drives p1 partition. The
> BTX loader stopped and could not load. This rendered my system
> 'un-bootable'. I copied this fi
Group:
I updated my amd64 computer today to r326622 and copied the
/boot/gptzfsboot file to each of my ZFS hard drives p1 partition. The
BTX loader stopped and could not load. This rendered my system
'un-bootable'. I copied this file from an earlier live filesystem CD,
which restored my compute
25 matches
Mail list logo
