Netgate SG-3100 and 2.5.0 - are there any stable snapshots we can try? (Or when will it be considered quasi-stable for homelab use?)
-
Hi,
I have a Netgate SG-3100.
I thought I'd try an upgrade to the 2.5.0 snapshots. (I'd previously tried here back in April 2019, but it kept crashing).
Anyhow, I was able to do the update, and reboot the box. I then thought I'd try a factory reset, and run through the setup wizard again. However, after finishing the wizard, the serial console was constantly spammed with the following message:
pfr_unroute_kentry: delete failed.
and I had to reboot the box.
After coming back up, I got these error messages:
__ _ __ / _|___ ___ _ __ ___ ___ | '_ \| |_/ __|/ _ \ '_ \/ __|/ _ \ | |_) | _\__ \ __/ | | \__ \ __/ | .__/|_| |___/\___|_| |_|___/\___| |_| Welcome to pfSense 2.5.0-DEVELOPMENT... ...ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/ipsec /usr/local/lib/perl5/5.30/mach/CORE Soft Float compatibility ldconfig path: done. >>> Removing vital flag from php73... done. 2019-12-01T05:49:14.278652+00:00 php-fpm 362 - - /ecl.php: No config.xml found, attempting last known config restore. 2019-12-01T05:49:14.280046+00:00 php-fpm 362 - - /ecl.php: New alert found: No config.xml found, attempting last known config restore. 2019-12-01T05:49:14.289211+00:00 php-fpm 362 - - /ecl.php: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:14.293550+00:00 php-fpm 362 - - /ecl.php: New alert found: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:14.324912+00:00 php-fpm 362 - - /ecl.php: XML error: no pfsense or pfsense object found! 2019-12-01T05:49:14.325807+00:00 php-fpm 362 - - 2019-12-01T05:49:14.327243+00:00 php-fpm 362 - - /ecl.php: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:14.330847+00:00 php-fpm 362 - - /ecl.php: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml External config loader 1.0 is now starting... mmcsd0s1 mmcsd0s2 mmcsd0s2a Launching the init system..... Warning: fopen(): Filename cannot be empty in /etc/inc/notices.inc on line 74 Warning: fopen(): Filename cannot be empty in /etc/inc/notices.inc on line 74 . Warning: fopen(): Filename cannot be empty in /etc/inc/notices.inc on line 74 ... done. Initializing.................. done. Starting device manager (devd)...2019-12-01T05:49:19.433341+00:00 php-fpm 362 - - /rc.linkup: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.433909+00:00 php-fpm 362 - - /rc.linkup: New alert found: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.433710+00:00 php-fpm 363 - - /rc.linkup: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.434586+00:00 php-fpm 363 - - /rc.linkup: New alert found: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.434615+00:00 php-fpm 362 - - /rc.linkup: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.438981+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.439133+00:00 php-fpm 362 - - /rc.linkup: New alert found: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.439680+00:00 php-fpm 362 - - /rc.linkup: XML error: no pfsense or pfsense object found! 2019-12-01T05:49:19.442908+00:00 php-fpm 362 - - 2019-12-01T05:49:19.443025+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.443961+00:00 php-fpm 363 - - /rc.linkup: XML error: no pfsense or pfsense object found! 2019-12-01T05:49:19.444133+00:00 php-fpm 363 - - 2019-12-01T05:49:19.444196+00:00 php-fpm 362 - - /rc.linkup: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.448115+00:00 php-fpm 362 - - /rc.linkup: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.448987+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.452627+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.566738+00:00 php-fpm 363 - - /rc.linkup: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.569692+00:00 php-fpm 363 - - /rc.linkup: New alert found: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.570368+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.570827+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.574335+00:00 php-fpm 363 - - /rc.linkup: XML error: no pfsense or pfsense object found! 2019-12-01T05:49:19.574470+00:00 php-fpm 363 - - 2019-12-01T05:49:19.575645+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.578963+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.585076+00:00 php-fpm 363 - - /rc.linkup: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.588441+00:00 php-fpm 363 - - /rc.linkup: New alert found: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.589179+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.593051+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.593570+00:00 php-fpm 363 - - /rc.linkup: XML error: no pfsense or pfsense object found! 2019-12-01T05:49:19.593713+00:00 php-fpm 363 - - 2019-12-01T05:49:19.594885+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.597716+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.603705+00:00 php-fpm 363 - - /rc.linkup: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.607162+00:00 php-fpm 363 - - /rc.linkup: New alert found: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.607830+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.608334+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.611774+00:00 php-fpm 363 - - /rc.linkup: XML error: no pfsense or pfsense object found! 2019-12-01T05:49:19.611911+00:00 php-fpm 363 - - 2019-12-01T05:49:19.613081+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.616455+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.622441+00:00 php-fpm 363 - - /rc.linkup: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.625986+00:00 php-fpm 363 - - /rc.linkup: New alert found: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.626690+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.630699+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.631302+00:00 php-fpm 363 - - /rc.linkup: XML error: no pfsense or pfsense object found! 2019-12-01T05:49:19.634808+00:00 php-fpm 363 - - 2019-12-01T05:49:19.636062+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.639923+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.645940+00:00 php-fpm 363 - - /rc.linkup: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.649370+00:00 php-fpm 363 - - /rc.linkup: New alert found: No config.xml found, attempting last known config restore. 2019-12-01T05:49:19.650103+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.653990+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /conf/backup/config-1560674342.xml 2019-12-01T05:49:19.654559+00:00 php-fpm 363 - - /rc.linkup: XML error: no pfsense or pfsense object found! 2019-12-01T05:49:19.654719+00:00 php-fpm 363 - - 2019-12-01T05:49:19.659432+00:00 php-fpm 363 - - /rc.linkup: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml 2019-12-01T05:49:19.663450+00:00 php-fpm 363 - - /rc.linkup: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1560674342.xml done. Loading configuration......done. Updating configuration... Warning: Cannot use a scalar value as an array in /etc/inc/config.lib.inc on line 358 Warning: Cannot use a scalar value as an array in /etc/inc/config.lib.inc on line 383 . Warning: Cannot use a scalar value as an array in /etc/inc/config.lib.inc on line 383 . Warning: Cannot use a scalar value as an array in /etc/inc/config.lib.inc on line 383
and the "Cannot use a scalar value as an array" message was repeatedly continuously. (Might be related to this post?)
So pfSense 2.5.0 seems like a no-go on the SG-3100 right now.
However, does anybody know a working dev snapshot that works on the SG-3100? And how you might go about flashing this snapshot directly?
Or any idea when the Netgate appliances (e.g. SG-3100, XG-7100) might have stable pfSense 2.5.0 images/installs?
-
I have 2.5.0 snapshots running on two SG-3100s and it's fine here. What packages/features do you have enabled?
From that crash, I might suspect that you have FRR on there. There is currently a known issue with FRR and multi-path routing which seems to hit a couple people, especially with multiple IPv6 full BGP feeds. I haven't had an opportunity to reproduce it here yet, though.
-
This was actually a factory reset SG-3100 running the 2.5.0 snapshot from around December 2nd.
I'd simply run through the initial configuration wizard to set things like timezone, and root password - no configuration beyond that, or any packages installed.
I'm happy to try and update the SG-3100 to the latest snapshot again this week (would be great if there was an img we could flash directly), if you think it's worth a shot...
-
I tried it again today.
However, this time, I got a working config up in 2.4.4-p3 - then did the upgrade to version
2.5.0.a.20191206.0815
.I did not do a factory reset after the upgrade this time - and it seems to be OK this time.
I did notice on startup and during upgrade seeing a bunch of error messages around "Unable to load dynamic library" - e.g.:
Is this something I should be worried about?
Here is the output from the WebUI during the upgrade - https://gist.github.com/victorhooi/3e8b36d0e9adfddd65df4dafc49e5734
Here is the serial console output during the upgrade - https://gist.github.com/victorhooi/f8c8c6815b141dcdb86e0df355267cc9
-
Those errors are expected during upgrade as components of the system are upgraded. It's only a concern if they persist after the upgrade completes.
https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html#upgrading-from-versions-older-than-pfsense-2-5-0
-
Hey guys, hope you are doing fine, I tried to upgrade my SG-3100 to the 2.5 development version, and after the reboot, got a bunch of errors showed in the attached .txt file.
I did the update through the System/UpdateSystem/Update from 2.4.4p3.
I have recovered successfully to 2.4.4-p3 and it is working perfectly as it was before the update attempt, so no impact in my environment.
Is it possible to check the errors logs to point out what I could have done wrong?
I would like to try again.
pfsense_2.5_logs.txt -
@mcury said in Netgate SG-3100 and 2.5.0 - are there any stable snapshots we can try? (Or when will it be considered quasi-stable for homelab use?):
pfsense_2.5_logs.txt
"UFS /dev/diskid/DISK-D4EC8498s2a (/) cylinder checksum failed"
UFS == File system.
"DISK-D4EC8498s2a " = you 'hard' disk (or whatever drive a 3100 has).
CRC errors on read.- As of now, keep a copy of your config.xml.
- use the console access, and as soon as you see
| '_ \| |_/ __|/ _ \ '_ \/ __|/ _ \ | |_) | _\__ \ __/ | | \__ \ __/ | .__/|_| |___/\___|_| |_|___/\___| |_|
Hit 'any key' and goto single user mode. See manual - and run several fsck checks. This will show probably a lot of errors : the "cylinder checksum" is generated by the drive hardware .... and when reading back the sectors contains 'wrong bits' ....
These errors are not related to 2.5.0 or an upgrade or something like that.
It's just a system that has a very hard time to 'boot'. -
@Gertjan Thanks for your reply, I did as you said, boot -s to get into boot single mode, ran the /sbin/fsck -y / until it was marked as clean, but the problem persisted, same errors during boot.
So, back to 2.4.4-p3, anyways, thanks for pointing me that out.
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225110
-
There aren't any known issues with 2.5.0 on SG-3100 at the moment. I'm running it on two of them. There are problems with 2.4.5 yet that are being worked on, but 2.5.0 should be OK for the moment. You might actually have a hardware issue there that maybe isn't being hit in the same way by 2.4.4, or it might be a bug in FreeBSD 12.0 that will be resolved once the 2.5.0 base is moved to 12.1/12-STABLE.
If you are OK on 2.4.4 then it is likely fine, but keep an eye on it.