Upgrade from 2.7.0 to 2.7.2: boot loop issue
-
Hi,
I run since several years Pfsense on a Zotac ZBOX-ID89 : https://www.zotac.com/old_zotac/index.php?id=170160&L=0&tx_zoprodisp_pi1%5Bel%5D=10&tx_zoprodisp_pi1%5Bproduid%5D=5191
1. First, I had an issue to update it from console:
0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option: 13 ERROR: It was not possible to determine pkg remote version >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package repository pfSense-core has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package repository pfSense has no meta file, using default settings pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package Unable to update repository pfSense Error updating repositories! ERROR: It was not possible to determine pfSense-upgrade remote version ERROR: It was not possible to determine pfSense-upgrade remote version >>> Upgrading pfSense-upgrade... failed.2. So I ran "certctl rehash"
Scanning /usr/share/certs/untrusted for certificates... Scanning /usr/share/certs/trusted for certificates... Scanning /usr/local/share/certs for certificates...3. And could run the update:
update log4. But it never came back from reboot.
Since I am away from this Pfsense, I asked a local user who sent me some videos and pictures: there is a boot loop, but I don't know why and how to fix it remotely (or giving basic instructions to non IT users).The pictures and video: https://imgur.com/a/DDhXP8o
Could you please help me?
Thanks in advance for your kind help!
-
Hmm, that looks like it tries to switch to the EFI console and then has an issue. An issue sufficiently bad that it just reboots.
Did it have a monitor attached when it first failed?
I have seen devices fail when trying to use 4K because it's a default. -
@stephenw10 thanks for your quick answer.
As far as I know, the screen was only connected after the issue happened, to check if there were some relevant error messages.
So no screen connected before this issue. -
Hmm, we've seen a few systems present like that. Mostly virtualised. However I've never seen a system reset like that when it did.
Does that system have a com port? Is it enabled?
-
@stephenw10 This one is not virtualized.
This Zotac has indeed a com port:
It is maybe enable in the BIOS, but :- there is nothing plugged in this port
- this config has not changed and worked perfectly before this upgrade attempt.
-
Hmm, can you check the serial console?
Can you try booting legacy instead of UEFI?
-
@stephenw10 It was already set to Legacy only:
So I made it changed to UEFI:
Which solved the boot loop, so Pfsense could finish its upgrade:
And voila, it was a relief to see this prompt!
Thanks for your kind help stephen in finding the solution remotely, you saved me a 3-hour drive!
-
Huh. Well that's unexpected. It was clearly loaded the EFI console previously. https://imgur.com/4lH0PK0
Good result though.
