2.7.0 upgrade crash
-
Thank you for the suggestion. I looked at the two xml files and the NICs were identical.
After a lot of playing around, I accidently got 2.7.0 installed. The problem was that during the installation process, I was specifying GPT formatting for the disk. Using MSDOS formatting instead solved the problem.
Now why using GPT formatting would cause a problem only after I restored the configuration file is a mystery to me.
Art
-
@aiz said in 2.7.0 upgrade crash:
Now why using GPT formatting would cause a problem only after I restored the configuration file is a mystery to me.
It wouldnt.
-
Ryan,
I have two nearly identical boxes. They both act the same. If I install 2.6.0 using GPT and restore my configuration, both work fine. If I install 2.7.0 using GPT and restore my configuration, they both crash on boot up. If I install 2.7.0 using MSDOS MBR and restore my configuration, it works fine.
I tried to upload a screenshot of the boot crash. It's the first time I've tried to load an image.
This is pretty weird behavior. My system is working, but I'm curious to understand how a pfSense configuration restore can affect a boot sequence.
Art
-
@aiz I know one upgrade version for me automatically went to using ZFS filesystem. Again that was a long time ago, before that I had UFS. maybe your upgrade partitioned the drive differently. You old enough to remember FDISK for MS DOS 3.12 when you had to partition the drive correctly to install the software and get command.com installed? Now drawing connections to this issue maybe it has different a filesystem. Check if it's UEFI or lacacy in the BIOS/CMOS settings when the machine boots
-
Thank you for your thoughts. The installation memstick actually has two entry points for the boot to install. One of them leads to an installation that says that MSDOS MBR won't be bootable "in this platform" or something like that. The other allows you to use MSDOX MBR and it is bootable.
In any case, I still don't understand how a configuration file can cause a boot to fail.
Your are right. I do remember the good old days -- the first computer I programmed used punched paper tape!
Art
-
@aiz And after booting the paper tape you loaded the card deck on the card reader (probably FORTRAN).
Ted
-
-
@aiz I remember when UEFI started to be more prevalent some machines would no longer boot unless set to legacy. USB flash drives would have to set to specific speeds to be read by the boot process, UEFI does link into the boot process more than in the past and could be the reason for the issues. DOS based (Fat 16) (Fat 32) (NTFS) partitioned drives that originally installed with the newer software that now contains upgrades to UEFI requirements would cause issues. Have you attempted to backup the configuration and do some repartitioning with some new SSD drives after do a fresh install after you enabled UEFI in the system BIOS? That might fix a lot of issues, you could use ZFS at that point.
I use to have 10k rpm SCSI drives that sounded like a 747 when they ran, it was wicked cool. Today SSD drives don't make a sound.
-
The there was the 500M word (24 bit) drum we had on the SDS-930. Those were the days!
You could be right on the UEFI.
Thanks.
-
@aiz my first PC was a At&T PC 6300 that rocked a 10MB drive ran DOS 3.11. I loved playing with autoexect.bat and config.sys files adding different drivers and menus so it would auto configure when it booted it was so cool. I use to have something called MS-DOSSHELL not the shell like today, it was a windows type file program that my mouse with would work with. Load mem upper, echo off, all sorts of fun when I was younger I was elementary school aged. I had this cool sound blaster 16 ISA card with a talking parrot and a microphone. Screen was monochrome green. I would research UEFI in your BIOS. You may need a reinstall with it enabled. Low level formats took forever remember those? When y2k was announced I thought everyone was crazy as it just rolled back over because I tested it before hand with my old system
-
@aiz I just took a class on assembly code. Amazing stuff.
-
I think you put your finger on the problem. The boxes I have were purchased in 2015. UEFI???? I'll take a look. But I still wonder why they booted fine before I restored the configuration and wouldn't boot after I restored the configuration. That was true if I used one of the install boots (MSDOS??) and not the other (UEFI???) boot. Wish I knew more about this. But I'll do some digging.
My first "PC" was a Xerox 820 and then an 860 and then an IBM PC. Thanks for the memories.
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
Is that screenshot where it appeared to hang after restoring the config?
More commonly after restoring a config is to end up with the wrong console set as primary. Usually the last thing shown will be the NICs linking for example.
Steve
-
The screen shot is what happened during the reboot after the configuration restore.
Thanks for your interest.
Art
-
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
