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

stephenw10

Yeah, it shouldn't do that. We're looking into it now but I believe that's fixed in the next installer version.

nalims

So it actually boots into pfsense somewhat, I see the Welcome to pfSense page in the terminal.

When I press 1 for Boot Multi user [Enter] it loads some stuff but apparently fails to mount the disk:

[...]
Trying to mount root from zfs:pfSense/ROOT/default []...
Mounting from  zfs:pfSense/ROOT/default failed with error 2: unknown file system.
[...]

And then it drops me to a mountroot> command line interface.

stephenw10

Hmm, maybe didn't add the required loader values because it aborted the script.

Try escaping to the OK> prompt at the boot loader and then entering:

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

If that successfully boots you can add those variables to the loader file.

nalims

Wow, this worked! <3

I was able to boot to pfSense 2.7.2, and I'm getting an ip on the LAN, awesome!

Could you tell me how I can add those (which exactly?) variables to the loader file?

stephenw10

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.

nalims

Wonderful, thank you very much!

Frequency

Hello,

Thank you for the help so far. I've also got a similar issue, a Protectli FW4C device with Coreboot bios which finished it's installation with the same error message "Failed to run post installation script".
' Install error.jpg

I am using the default required boot option, ZFS so doubt its a UEFI issue.

I have managed to boot the machine by exiting from the pfsense autoselect options and then running Stephenw10's commands as per Using boot commands provided.jpg

When editing the /boot/loader.conf to add the two lines below or as suggested in the /default/loader.conf file, creating a new /boot/loader.conf.local file with just the two lines the Normal reboot still fails to autoboot to pfsense and gets stuck on Mountroot>

Reboot even with loader.conf file settings set.jpg

opensolaris_load="YES"
zfs_load="YES"

Happy to provide any log files required, unfortunately I cannot find the install-log.txt file in the /tmp/ directory now pfsense is installed, hence the screenshots.

Am I editing the wrong file, or missing something? Adding the two lines hasn't fixed the automatic boot to pfsense.

Thank you

stephenw10

Do you see it loading those modules at boot? Should show at the console before the kernel loads.

Frequency

@stephenw10 This is what I see at boot - Kernel and Solaris.ko seem to be there, but not ZFS_ ?

Boot modules.jpg

Frequency

OK I shall admit the problem is between the chair and the keyboard. Happy Monday.

Looked at the zfs line, and had _Load instead of _load.

Capital latter=problem in linux world. Excuse my windows background ;-)

Thanks @stephenw10 !

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?