Re: Newly upgraded -CURRENT box does not boot

[John Baldwin]

On 8/21/18 4:19 AM, Kyle Evans wrote:
> On Mon, Aug 20, 2018 at 4:27 PM, Brett Gmoser
>  wrote:
>> Hi there,
>>
>> I was told to e-mail these addresses with this.
>>
>> I did an `svn update` on /usr/src last night, build world and kernel as
>> usual. This morning I installed the kernel, booted into single user,
>> installed world and did mergemaster -Ui as usual. The new kernel had booted
>> fine. Upon reboot, the machine will no longer boot:
>>
>> Startup error in /boot/lua/loader.lua:
>> LUA ERROR: cannot open /boot/lua/loader.lua: no such file or directory
>>
>> can't load 'kernel'
>>
>> Many things in the bootloader do not work, including "boot kernel.old", "ls
>> /boot", and various other things (most if not all just result in "Command
>> failed"). Interestingly, "ls /mnt" works, other directories do not. That's
>> the only clue I have.
>>
>> I'm able to reboot in an installer image and mount the drive just fine.
>> Everything is there and is as expected, including /boot/lua/loader.lua.
>>
>> I re-installed everything in /usr/src/stand (chroot'd on the installer
>> image, and "cd /usr/src/stand && make clean all install"). This did not fix
>> the problem.
>>
>> Does anybody happen to have any ideas?
>>
> 
> To briefly follow up and summarize the current standing here following
> some more discussion/attempts to fix on IRC:
> 
> 1.) x86 BIOS boot
> 2.) Problem appears for both forthloader and lualoader
> 3.) Early March loader works, recent loader does not [Only tried
> loader from the past ~day]
> 4.) ls / works, ls /mnt works, ls /boot and other directories fails
> 5.) However, /boot is confirmed intact and populated by booting via
> 11.2 install media and inspecting local disk
> 
> We'll hopefully be having a bisect session tomorrow to figure out
> where exactly this broke so that maybe Brett has a chance to upgrade
> to 12.0, unless this sounds familiar to someone and the cause is
> obvious. =)

I would start with bisecting the changes to libi386/biosdisk.c.  Also,
comparing 'lsdev -v' output between old and new loaders might be a useful
step before starting on the bisecting.

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Newly upgraded -CURRENT box does not boot

[Kyle Evans]

On Mon, Aug 20, 2018 at 4:27 PM, Brett Gmoser
 wrote:
> Hi there,
>
> I was told to e-mail these addresses with this.
>
> I did an `svn update` on /usr/src last night, build world and kernel as
> usual. This morning I installed the kernel, booted into single user,
> installed world and did mergemaster -Ui as usual. The new kernel had booted
> fine. Upon reboot, the machine will no longer boot:
>
> Startup error in /boot/lua/loader.lua:
> LUA ERROR: cannot open /boot/lua/loader.lua: no such file or directory
>
> can't load 'kernel'
>
> Many things in the bootloader do not work, including "boot kernel.old", "ls
> /boot", and various other things (most if not all just result in "Command
> failed"). Interestingly, "ls /mnt" works, other directories do not. That's
> the only clue I have.
>
> I'm able to reboot in an installer image and mount the drive just fine.
> Everything is there and is as expected, including /boot/lua/loader.lua.
>
> I re-installed everything in /usr/src/stand (chroot'd on the installer
> image, and "cd /usr/src/stand && make clean all install"). This did not fix
> the problem.
>
> Does anybody happen to have any ideas?
>

To briefly follow up and summarize the current standing here following
some more discussion/attempts to fix on IRC:

1.) x86 BIOS boot
2.) Problem appears for both forthloader and lualoader
3.) Early March loader works, recent loader does not [Only tried
loader from the past ~day]
4.) ls / works, ls /mnt works, ls /boot and other directories fails
5.) However, /boot is confirmed intact and populated by booting via
11.2 install media and inspecting local disk

We'll hopefully be having a bisect session tomorrow to figure out
where exactly this broke so that maybe Brett has a chance to upgrade
to 12.0, unless this sounds familiar to someone and the cause is
obvious. =)

Thanks,

Kyle Evans
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Newly upgraded -CURRENT box does not boot

[Warner Losh]

On Mon, Aug 20, 2018 at 5:24 PM, Brett 
wrote:

> On 8/20/2018 7:09 PM, Warner Losh wrote:
>
>> On Mon, Aug 20, 2018 at 4:50 PM, Brett 
>> wrote:
>>
>> Hi Kevin,
>>>
>>> Thanks for your help.
>>>
>>> Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make
>>> LOADER_DEFAULT_INTERP=4th installkernel"?
>>>
>>> Nope. Kernel has nothing to do with it. That won't work.
>>
>> I had also previously tried " make clean all install
>>
>>> WITHOUT_LUA_LOADER=yes" in /usr/src/stand which did not help.
>>>
>>> You could just do "ln -sf /boot/loader_4th /boot/loader" and reboot if
>> that's the issue. Or at the boot2 prompt, you could type in
>> /boot/loader_4th if you haven't booted yet.
>>
>> You could also do a simple 'make install LOADER_DEFAULT_INTERP=4th" which
>> does approximately the same thing.
>>
>> Though why you'd get loader.lua not found is kinda crazy
>>
>> Warner
>>
> Hi Warner,
>
> I've tried those things, unfortunately none of them worked. With forth,
> things are slightly different (no more lua error), but ultimately the same
> result: - the kernel doesn't load ("can't load 'kernel'").
>
> I lastly tried "ln -sf /boot/loader_4th /boot/loader", now I get "No
> /boot/loader" and a boot: prompt. I can do "boot/loader_4th" which will use
> the forth loader with the results the same as the above.
>
> Any help is appreciated - this is a very important box unfortunately. :(
>

If both /boot/loader_lua and /boot/loader_4th fail in the same way, you may
be in trouble. There's a sliver of a chance that /boot/loader_simp might
work, but if the other two both fail, it's something common between them
that's likely shared by /boot/loader_simp.

I'd install old /boot/loader and then try to bisect where things went wrong
from your last update. Thankfully, it looks like the last known good one
for you was in March, and all versions since then you can rebuild just
src/stand w/o doing a full world so it should be quick to trace down. There
are maybe 20,000 svn changes or so, which should zero in on the right one
in about 17 tries... It takes me about a minute to build, so with luck
you'll know in about an hour...

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Newly upgraded -CURRENT box does not boot

[Brett]

On 8/20/2018 7:09 PM, Warner Losh wrote:

On Mon, Aug 20, 2018 at 4:50 PM, Brett 
wrote:


Hi Kevin,

Thanks for your help.

Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make
LOADER_DEFAULT_INTERP=4th installkernel"?


Nope. Kernel has nothing to do with it. That won't work.

I had also previously tried " make clean all install

WITHOUT_LUA_LOADER=yes" in /usr/src/stand which did not help.


You could just do "ln -sf /boot/loader_4th /boot/loader" and reboot if
that's the issue. Or at the boot2 prompt, you could type in
/boot/loader_4th if you haven't booted yet.

You could also do a simple 'make install LOADER_DEFAULT_INTERP=4th" which
does approximately the same thing.

Though why you'd get loader.lua not found is kinda crazy

Warner

Hi Warner,

I've tried those things, unfortunately none of them worked. With forth, 
things are slightly different (no more lua error), but ultimately the 
same result: - the kernel doesn't load ("can't load 'kernel'").


I lastly tried "ln -sf /boot/loader_4th /boot/loader", now I get "No 
/boot/loader" and a boot: prompt. I can do "boot/loader_4th" which will 
use the forth loader with the results the same as the above.


Any help is appreciated - this is a very important box unfortunately. :(

Thanks,

-Brett

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Newly upgraded -CURRENT box does not boot

[Warner Losh]

On Mon, Aug 20, 2018 at 4:50 PM, Brett 
wrote:

> Hi Kevin,
>
> Thanks for your help.
>
> Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make
> LOADER_DEFAULT_INTERP=4th installkernel"?
>

Nope. Kernel has nothing to do with it. That won't work.

I had also previously tried " make clean all install
> WITHOUT_LUA_LOADER=yes" in /usr/src/stand which did not help.
>

You could just do "ln -sf /boot/loader_4th /boot/loader" and reboot if
that's the issue. Or at the boot2 prompt, you could type in
/boot/loader_4th if you haven't booted yet.

You could also do a simple 'make install LOADER_DEFAULT_INTERP=4th" which
does approximately the same thing.

Though why you'd get loader.lua not found is kinda crazy

Warner


> Thanks!
>
> -Brett
>
> On 8/20/2018 6:31 PM, Kevin Oberman wrote:
>
>> Check the archive of this list for the past 24 hours. The default bot was
>> just converted to the lua boot today and there have been some issues. The
>> "one liner" to switch back to the FORTH boot was posted to use to work
>> around this and I believe that the change will be rolled back until the
>> "corner cases" can be fixed.
>> http://lists.freebsd.org/pipermail/freebsd-current/
>> --
>> Kevin Oberman, Part time kid herder and retired Network Engineer
>> E-mail: rkober...@gmail.com 
>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>>
>>
>>
>> On Mon, Aug 20, 2018 at 2:28 PM Brett Gmoser <
>> freebsdcurr...@codexterous.com >
>> wrote:
>>
>> Hi there,
>>
>> I was told to e-mail these addresses with this.
>>
>> I did an `svn update` on /usr/src last night, build world and
>> kernel as
>> usual. This morning I installed the kernel, booted into single user,
>> installed world and did mergemaster -Ui as usual. The new kernel had
>> booted fine. Upon reboot, the machine will no longer boot:
>>
>>  Startup error in /boot/lua/loader.lua:
>>  LUA ERROR: cannot open /boot/lua/loader.lua: no such file or
>> directory
>>
>>  can't load 'kernel'
>>
>> Many things in the bootloader do not work, including "boot
>> kernel.old",
>> "ls /boot", and various other things (most if not all just result in
>> "Command failed"). Interestingly, "ls /mnt" works, other
>> directories do
>> not. That's the only clue I have.
>>
>> I'm able to reboot in an installer image and mount the drive just
>> fine.
>> Everything is there and is as expected, including
>> /boot/lua/loader.lua.
>>
>> I re-installed everything in /usr/src/stand (chroot'd on the
>> installer
>> image, and "cd /usr/src/stand && make clean all install"). This
>> did not
>> fix the problem.
>>
>> Does anybody happen to have any ideas?
>>
>> Thanks,
>>
>> -Brett
>>
>> ___
>> freebsd-current@freebsd.org 
>> mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to
>> "freebsd-current-unsubscr...@freebsd.org
>> "
>>
>>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Newly upgraded -CURRENT box does not boot

[Brett]

Hi Kevin,

Thanks for your help.

Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make 
LOADER_DEFAULT_INTERP=4th installkernel"?


I had also previously tried " make clean all install 
WITHOUT_LUA_LOADER=yes" in /usr/src/stand which did not help.


Thanks!

-Brett

On 8/20/2018 6:31 PM, Kevin Oberman wrote:
Check the archive of this list for the past 24 hours. The default bot 
was just converted to the lua boot today and there have been some 
issues. The "one liner" to switch back to the FORTH boot was posted to 
use to work around this and I believe that the change will be rolled 
back until the "corner cases" can be fixed.

http://lists.freebsd.org/pipermail/freebsd-current/
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com 
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


On Mon, Aug 20, 2018 at 2:28 PM Brett Gmoser 
> wrote:


Hi there,

I was told to e-mail these addresses with this.

I did an `svn update` on /usr/src last night, build world and
kernel as
usual. This morning I installed the kernel, booted into single user,
installed world and did mergemaster -Ui as usual. The new kernel had
booted fine. Upon reboot, the machine will no longer boot:

 Startup error in /boot/lua/loader.lua:
 LUA ERROR: cannot open /boot/lua/loader.lua: no such file or
directory

 can't load 'kernel'

Many things in the bootloader do not work, including "boot
kernel.old",
"ls /boot", and various other things (most if not all just result in
"Command failed"). Interestingly, "ls /mnt" works, other
directories do
not. That's the only clue I have.

I'm able to reboot in an installer image and mount the drive just
fine.
Everything is there and is as expected, including
/boot/lua/loader.lua.

I re-installed everything in /usr/src/stand (chroot'd on the
installer
image, and "cd /usr/src/stand && make clean all install"). This
did not
fix the problem.

Does anybody happen to have any ideas?

Thanks,

-Brett

___
freebsd-current@freebsd.org 
mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org
"



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Newly upgraded -CURRENT box does not boot

[Brett Gmoser]

Hi there,

I was told to e-mail these addresses with this.

I did an `svn update` on /usr/src last night, build world and kernel as 
usual. This morning I installed the kernel, booted into single user, 
installed world and did mergemaster -Ui as usual. The new kernel had 
booted fine. Upon reboot, the machine will no longer boot:


    Startup error in /boot/lua/loader.lua:
    LUA ERROR: cannot open /boot/lua/loader.lua: no such file or directory

    can't load 'kernel'

Many things in the bootloader do not work, including "boot kernel.old", 
"ls /boot", and various other things (most if not all just result in 
"Command failed"). Interestingly, "ls /mnt" works, other directories do 
not. That's the only clue I have.


I'm able to reboot in an installer image and mount the drive just fine. 
Everything is there and is as expected, including /boot/lua/loader.lua.


I re-installed everything in /usr/src/stand (chroot'd on the installer 
image, and "cd /usr/src/stand && make clean all install"). This did not 
fix the problem.


Does anybody happen to have any ideas?

Thanks,

-Brett

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"