LUA ERROR: Can not open /boot/lua/loader.lua

uii

New Member

Thanks: 4
Messages: 18

#1
I tried to install Freebsd 12.0 RC3 and got the same error as mentioned here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233098
Also on a amd64 box.

"Startup error in /boot/lua/loader.lua:
LUA ERROR: Cannot open /boot/lua/loader.lua:
no such file or directory"
"can't load kernel"

Is there a solution to fix this? Never had a problem to install version 11.
I wonder if I will be able to install the upcoming release: 12.0?

Thanks for any advice.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Thanks: 6,785
Messages: 28,551

#4
Use the -RELEASE. The announcement should be in a few days[*], but the image is already available. The announcement will happen when all mirrors have caught up.

[*] Some time today actually.
 

GrandAdmiralThrawn

Member


Messages: 20

#6
I just upgraded from 11.2-RELEASE to 12.0-RELEASE, and now my system is broken in the exact same way. A simple ls /boot/ on the loader's terminal gives the message "open ´boot´ failed: no such file or directory". Is /boot/ empty, or somehow inaccessible? ls / still shows the directory to be present, but like most others its contents can't be listed.

Any idea on how this can be fixed?

Edit: Out of curiosity I tried to install from FreeBSD-12.0-RELEASE-amd64-dvd1.iso, as this is not a critical machine. Same thing happens even with a completely clean install.
 

xtaz

Well-Known Member

Thanks: 92
Messages: 380

#7
I upgraded three 11.2 systems to 12.0 last night and had no issues. These are running ZFS, but only on a single disk without any mirroring or ZRAID. This means that the standard installer puts /boot on the same dataset as /. If you have a mirror/ZRAID I believe the installer creates a new dataset specifically for /boot? I'm wondering if that may have something to do with the issue you guys are seeing.
 

GrandAdmiralThrawn

Member


Messages: 20

#8
Hm, I'm using UFS, and everything is on one disklabel. It's an older BIOS-based machine in my case.

Edit: There is one more thing. When booting from the installation medium, or attempting to boot 12.0 from the system disk, when it lists the disks, it says something like "Error: Reading 1 to 0 on 1" or so, including a hex address (unure if the address points at RAM or disk). Not sure what the exact wording of the message was, but it looks like an I/O error. I just created a FreeBSD 11.2-RELEASE installation medium, and it doesn't show that message at all.

Will install 11.2 now to see whether it's a hardware issue or not.

Edit 2: Alright, 11.2 works. 12.0 doesn't, neither as an upgrade, nor as a fresh installation (to UFS on a BSD disklabel).
 

Polyatomic

Member

Thanks: 11
Messages: 28

#10
Right honorable operators, salute. I have a mind to try FreeBSD-12.0-RELEASE using MBR partitioning scheme and traditional BSD disklabel. Onwards I hope to reproduce the above labouring under difficulties. Coming after intence internalization, I shall plan for deliverance of evil (in all honesty this could take a month of Sundays).
 

scottro

Daemon

Thanks: 451
Messages: 1,309

#11
Yup ran into this on a clean install, one other disk in the machine that shouldn't have been touched.
There's a bug report someone made but no answer to it yet.
 

scottro

Daemon

Thanks: 451
Messages: 1,309

#12
Ok, in my case, I fixed it by choosing MBR for Boot. I'd had GPT, and I don't feel like playing with it at this point, MBR will work fine for me on this machine.
 

GrandAdmiralThrawn

Member


Messages: 20

#13
I guess next time I'm making a full backup of my FreeBSD notebook before attempting an upgrade to 12.x. :p

Because, upon reinstallation of 11.2 I chose to install to BSD disklabels again.
 

Trihexagonal

Daemon

Thanks: 725
Messages: 1,295

#14
Using the FreeBSD-12.0-RELEASE-amd64-memstick.img medium with UFS and BSD Partitioning I got the same error about not being able to load the kernel. I went with UFS and MBR and populating my ports tree now.

My em0 card was recognized without any problems.
 

fernandel

Aspiring Daemon

Thanks: 154
Messages: 689

#15
So many problems with 12.0. Looks like is better to wait for 12.1? I am ready to install from scratch and I have redy FreeBSD-12.0-RELEASE-amd64-memstick.img but after all that reading I think it is safer to put on 11.2 which worked for me long time.
 

Moebius

New Member


Messages: 6

#16
I have the same problem on FreeBSD in Hyper-V after 12.0-RELEASE upgrade.
What is the currdev and loaddev values from command 'show' in loader prompt ?
Is it normal to have different values that from lsdev returns ?
What is the right way to fix correct values for currdev and loaddev ?
 
Top