2.7.2 Fresh install fails: "Failed to run the post installation script"

stephenw10

Cool. Easy fix!

robboroom

@stephenw10 said in 2.7.2 Fresh install fails: "Failed to run the post installation script":

Ok check the file: /boot/loader.conf

Those values may already have been added by pfSense when it booted. It should contain the lines:
opensolaris_load="YES"
zfs_load="YES"
If not add them there.

Hi, new here, exact same problem as topic starter, also on protectli vault.
Apparently the new installer isn't here.

I am a n00b at Pfsense, just getting my feet wet, so please forgive my noobness.
But how do I edit the /boot/loader.conf file?

stephenw10

Once it has booted you can use Diag > Edit File.

At the command line you can use the Easy Editor, ee. So:
ee /boot/loader.conf

Steve

robboroom

@stephenw10 Thank you, but still a couple of questions.

I end up at the command prompt in the mountroot directory
mountroot>

When I enter ee /bootloader.conf I get:
"Invalid file system specification"

When I enter Diag I get the same.

stephenw10

To make it boot initially you have to set the values at the bootloader (OK>) prompt as I showed here: https://forum.netgate.com/post/1173457

Only once it has booted fully can you edit the loader.conf file.

Frequency

Just to add to this thread, I'm sure I tried using vi to edit the conf file and although it looked edited, it didn't work. Instead after I managed to boot into pfsense by running the commands Stephen10 suggested

load /boot/kernel/kernel
load /boot/kernel/opensolaris.ko
load /boot/kernel/zfs.ko
boot

I was able to connect to the pfsense device using winSCP on the same network via my windows laptop (or SCP for non windows) and created the /boot/loader.conf.local file with the two entries:

opensolaris_load="YES"
zfs_load="YES"

Hope this helps someone who might use this route.

stephenw10

This is one of the only situations where I would recommend putting them in loader.conf directly. That is where they would normally be.

However putting them in loader.conf.local won't hurt anything.

robboroom

@stephenw10 said in 2.7.2 Fresh install fails: "Failed to run the post installation script":

To make it boot initially you have to set the values at the bootloader (OK>) prompt as I showed here: https://forum.netgate.com/post/1173457

Only once it has booted fully can you edit the loader.conf file.

Ok, but after I enter the lines at the ok prompt and I boot, I get to a screen with 17 options (0-16):
0) Logout

Assign interfaces
Set interface IP address
etc.

No possible option to enter ee /bootloader.conf

Again, so sorry for my ultimate noobness

stephenw10

Use option 8 there to reach the command line first.

robboroom

@stephenw10 said in 2.7.2 Fresh install fails: "Failed to run the post installation script":

Use option 8 there to reach the command line first.

Ah, THANK YOU, that worked.
It appeared I didn't have a bootloader.conf file, so I created a new one with the two lines.

After that I rebooted. Problem then was I still didn't autoboot to pfsense, but I managed to change the boot order and now it loads pfsense immediately and I end up at the command line to the mountroot> prompt.

Is this correct?

stephenw10

Ah, looks like you created a file in the wrong location. The file definitely exists but the correct command is:
ee /boot/loader.conf

...which it looks like I typo'd above.

robboroom

@stephenw10 said in 2.7.2 Fresh install fails: "Failed to run the post installation script":

Ah, looks like you created a file in the wrong location. The file definitely exists but the correct command is:
ee /boot/loader.conf

...which it looks like I typo'd above.

lol, ok.
I will redo. Should I delete the other? And if so, how?

stephenw10

It doesn't matter the file will be ignored.

But you can remove it with rm /bootloader.conf

doncarajo

@stephenw10 said in 2.7.2 Fresh install fails: "Failed to run the post installation script":

https://forum.netgate.com/post/1173457

I am having similar problems to original poster on a Protectli VP2420. Trying to install pfsense plus. I have the same "efgi_get_Variable: Bad address" problem. Doing the following

load /boot/kernel/kernel
load /boot/kernel/opensolaris.ko
load /boot/kernel/zfs.ko
boot

doesn't get me very far just to a screen of text. I can not access the pfsense webpage. I am not overly familiar with what is going on or why there is an error but I'm pulling my hair out. All I'm trying to do is upgrade my hardware. What is the issue? How do I fix it? How do I know if pfsense is "booting"? What is the screen supposed to show?

doncarajo

@doncarajo I should I add I contacted Netgate support as I paid for pfsense plus and they cannot help with protectli hardware. They suggested I run the BIOS in legacy mode but Coreboot doesn't have an option for that. Ideas?

doncarajo

@doncarajo Ok. In case anyone needs this in the future. I changed the BIOS from opencore to AMI (https://kb.protectli.com/kb/how-to-use-flashli/) and the installer worked.

stephenw10

Do you have output it showed when it failed? It would be good to note some new failure mode if there is one.

doncarajo

@stephenw10 The output was pretty much the same as the original poster, except that doing the additional "load" steps didn't make pfsense boot fully so I couldn't go any further. Everything that I looked up seemed to be pointing to a BIOS issue so that's what made me change it and finally made it work.

Bob Orter

@doncarajo I am sorry to be butting into your conversation right now but I am experiencing a problem that is virtually identical to the one described at the top of this thread. Unfortunately, my tech skills are rather basic so I am having difficulty with the explanations given. I am trying to install pfSense CE on a brand new Protectli Vault FW4C equipped with Coreboot. I am getting the same error output described above. I apologize that I do not know what most of these terms like EFI and UEFI mean. But, given that my problem seems to be the very same I would very much appreciate careful instructions that a noob like me can follow in order to successfully get pfSense installed. After the bad address messages I cannot get the vault to boot into pfSense and I know next to nothing about editting boot configuration files but I am determined to do what I must for success here. Your assistance would be very much appreciated! Thank you.

stephenw10

The root of the issue there is that the Coreboot UEFI implementation does not include the APIs to return the boot variables to the OS when it queries them. The error causes the installer to drop out before it finishes adding the loader values. However you should be able to add them back manually.

Or, as I suggested, you could use the legacy CE installer image which should not be affected.

Steve