2.7.0 upgrade crash
-
And it hangs in the same place if you try to install 2.7 with GPT?
-
I believe that the hang was with GPT. The strange thing is that when I go into bios to select the memstick for boot, there were two choices. One allowed MSDOS MBR and the other said that MSDOS MBR was unbootable "with this platform" or something like that.
The crash occurred with GPT and with the version that said MSDOS MBR was unbootable. I hope this all makes sense. I really don't have much expertise here.
Art
-
The memstick can be booted EFI or Legacy BIOS and if your platform is configured to boot both it will show them as two choices.
The installer detects how it was booted and uses that to advise what install type can be booted. If your platform actually boots both it likely will work with either.Steve
-
@stephenw10
Thanks, I'm learning. When I boot in EFI with GPT, I get the crash after the restore. At least I am pretty sure that is the scenario.Art
-
OK so you boot EFI and install as GPT and that all works OK?
It then boots up OK and you restore the config in the GUI?
Then when it reboots it hangs at that screenshot above?
-
That's correct.
The other thing I will note is that when 2.7.0 came out, I tried the usual upgrade online. The result was the same crash after the upgrade was installed.
That's what led me to try a complete reinstall of the software.
Art
-
Hmm, well that pretty much must be a console setting in the config you're importing. Check the main <system> section at the top of the file for console values.
-
I'm afraid I'm not sure what to look for. However, I do see that the primary console setting is "serial". In fact the box I am using is "vga".
I'll change that and see what happens.
Thanks for the hint.
-
Yup, remove that line from the config so it uses the default console which looks like it's the EFI console there.
-
Your suggestion seemed very logical as it might explain the crash after the online update.
I removed the line in the configuration file and I also tried changing the line to designate "video" rather than "serial". Both gave the same result. Before the changes, the boot up stopped with a blank screen with a blinking cursor. After the changes, the boot up stopped with an alphanumeric graphic of the pfSense logo and a flashing cursor. The boot did not complete.
Since I am not seeing complaints from others, it looks like this is issue may be the result of a 10 year old bios in my Gigbox units. It appears that something is destroying the UEFI file when I do the configuration file restore.
I'll stick with bios. It will be interesting to see what happens during the next pfSense update.
Thanks for your suggestion and help.
