Are the SG-3100 performance fixes included in the 21.09 Snaps
-
I'd like to start running 21.09 on my SG-3100, I feel like you guys have been working on it awhile now, so most of the critical bugs should be gone.
Did the SG-3100 performance fixes get ported over into 21.09 from 21.05.1, or should we wait for awhile still until those get merged? I know some of them had to do with compiling the code for the 3100 differently.
-
That would be a big no idea. Tried to upgrade my sg-3100 to 21.09 since I saw all the bugs were gone and in feedback, and the install broke on this..
Number of packages to be installed: 2
Number of packages to be upgraded: 25
Number of packages to be reinstalled: 138The process will require 4 MiB more space.
[1/165] Reinstalling pcre2-10.37...
[1/165] Extracting pcre2-10.37: .......... done
[2/165] Reinstalling libxml2-2.9.12...
[2/165] Extracting libxml2-2.9.12: .......... done
[3/165] Reinstalling libargon2-20190702...
[3/165] Extracting libargon2-20190702: .......... done
[4/165] Reinstalling indexinfo-0.3.1...
[4/165] Extracting indexinfo-0.3.1: .... done
[5/165] Reinstalling readline-8.1.1...
[5/165] Extracting readline-8.1.1: .......... done
[6/165] Reinstalling php74-7.4.22_1...
[6/165] Extracting php74-7.4.22_1: .........panic: ufs_dirbad: /: bad dir ino 223866 at offset 1536: mangled entry
cpuid = 0
time = 1631569606
Uptime: 23s
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting... -
21.09 contains all of the fixes from 21.05.1 plus even more improvements.
The error you encountered is not related to 21.09. The filesystem on your device is corrupted.
The best way forward is to wipe and reload it. Send a message to TAC at https://go.netgate.com and ask for a recovery image.
-
@jimp Just tried off a fresh install of 21.05.1 yesterday - hung up same place, same error. There's no way my file system is corrupted on two different installs - this one kept retrying and even came back and said the file system is clean.
-
That error can only come from a corrupt filesystem. Could be the target (disk in the device), could be the source (the USB memstick). Small chance it could be hardware but usually the errors are different in that case.
Write the recovery image to a fresh USB stick and try it again that way.
-
@jimp OK, I'll give a new USB stick a try. I'll even have the tech support team send me a new 21.05.1 image just in case (and then I'll try 21.09 again). I just don't see how the USB could be causing the issue when it installs 21.05.1 fine, and I dont have any problems.
I'm no developer, but I'd think having a corrupted file system would show up day to day with 21.05.1 running.
-
Ok, got a brand new image from support, and used a brand new usb drive.
This time I got it to install, only to get this error. This is causing all outbound ipv4 traffic to fail, but ipv6 seems uneffected.
There were error(s) loading the rules: pfctl: DIOCADDRULENV: Operation not supported by device - The line in question reads [0]: @ 2021-09-15 13:25:58
